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

Delete config properties #45

Open
Emily-Jiang opened this issue Jan 27, 2022 · 1 comment
Open

Delete config properties #45

Emily-Jiang opened this issue Jan 27, 2022 · 1 comment
Labels
Milestone

Comments

@Emily-Jiang
Copy link
Contributor

As an application developer, deployer or tester or a framework developer or tester, I expect to be able to specify that a configuration property should be removed in the event that it would otherwise have a value, so that I can easily make necessary adjustments to the configuration at deployment or testing time.

Based on #27 (comment) with some modifications

@Emily-Jiang Emily-Jiang created this issue from a note in Jakarta Config Board (Use Cases) Jan 27, 2022
@Emily-Jiang Emily-Jiang added this to the 1.0 milestone Feb 10, 2022
@tomas-langer
Copy link
Contributor

We need to decide (architecture) of handling this

  • do we want to support this at all (maybe we can define configuration without the requirement to remove a property)
  • if we want to support it, will it be an integral part of config source features or an external feature ("special" source to delete properties?)

This must be decided for 1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

2 participants