2019-12-18 19:26:49 UTC - Addison Higham: :thinking_face: so currently, you can apply permissions to a namespace or a topic or a wildcard on the role name. Does have a wildcard for the topic suffix makes sense? Here is our use case, we have an app that receives messages from multiple other services where the service can write to arbitrary topics but they must be prefixed with the service name (like `<persistent://tenant/my-app/><service>-free-form-string` ). The reason for doing this instead of namespaces is because then we can just do a single regex subscription of `<persistent://tenant/my-app/*>` , with multiple namespaces, we know need to enumerate all the different services in our app and manage multiple consumers.
The design seems to work well, except that permissions can only be applied to a namespace or to a fully qualified topic. If permissions could be applied to a prefix of a topic, that would make this ideal, but for now, we would still make it work by adding permissions per topic ---- 2019-12-18 21:25:41 UTC - Nick Nezis: @Nick Nezis has joined the channel ---- 2019-12-19 04:54:28 UTC - shcho: @shcho has joined the channel ----
