Support custom properties for Tenants and Namespaces

[eolivelli]

Search before asking

• I searched in the issues and found nothing similar.

Motivation

In Pulsar 2.11 we can store custom properties in Topics and in Subscription.
We lack the ability to tag Tenants and Namespaces with custom properties.

Solution

Support setting a custom set of key-value pairs on Tenants and on Namespaces.

The map can be immutable

Alternatives

No response

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[dao-jun]

related PIP: #12629

[michaeljmarshall]

We'll need to consider authorization for these properties. Who has access to the get and modify these properties?

[michaeljmarshall]

For reference, reading topic properties maps to the TopicOperation.GET_METADATA, which requires lookup permission for the topic. Updating or deleting that metadata require tenant admin or superuser privileges. Interestingly, any user that can create a topic can also create the initial properties map for that topic. That is technically inconsistent since a role could have permission to create a properties map but not update it later.

In the context of this feature, I think it seems reasonable for a tenant admin or superuser should be able to create/update/delete namespace properties, and I think a super user should be the only role that is able to create/update/delete tenant properties.

[github-actions]

The issue had no activity for 30 days, mark with Stale label.