Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit the scope of valid properties to the service they apply to #2855

Open
pepone opened this issue Oct 4, 2024 · 0 comments
Open

Limit the scope of valid properties to the service they apply to #2855

pepone opened this issue Oct 4, 2024 · 0 comments
Assignees
Labels
Milestone

Comments

@pepone
Copy link
Member

pepone commented Oct 4, 2024

We recently introduced language specific properties, which allows to narrow the scope of properties.

It would be good to have a similar mechanism for "service" specific properties. It doesn't make sense that all C++ applications accept "Glacier2" properties as valid.

We can have a set of "enabled" prefixes, for example Ice, IceSSL should be always enabled and validated.

Others Glacier2, IceGrid, IceStorm should be "reserved" but "disabled", if an application sets such a property its an error.

Then we need a way to enable, the additional prefixes, in which case we validate that the properties are valid.

@pepone pepone added the proposal label Oct 4, 2024
@bernardnormier bernardnormier added this to the 3.8.0 milestone Oct 4, 2024
@externl externl self-assigned this Oct 21, 2024
externl added a commit that referenced this issue Oct 30, 2024
Updates the generated PropertyNames to indicate if a property array is opt-in. Properties whose prefix is opt-in can now no longer be set unless the corresponding Property object is constructed with an opt-in list containing its prefix.

I've also renamed UnknownPropertyException to PropertyException so we can use it for a few more things.

Part of #2855
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants