-
Notifications
You must be signed in to change notification settings - Fork 159
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
add properties.discovery.yaml support #2740
Conversation
These properties can be in `config.d/properties.discovery.yaml` or specified at run time with `--set` command line options. | ||
|
||
Each discovery property also has an equivalent environment variable form using `_x<hex pair>_` encoded delimiters for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I plan on adding a cli helper of some kind in the future to make producing these env vars possible for the user similar to what we offer in the bundle.d template helpers.
494a254
to
f587a65
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for all of the discovery property examples and clear priority list for different ways to supply properties, super helpful!
internal/confmapprovider/discovery/testdata/invalid-properties.d/properties.discovery.yaml
Outdated
Show resolved
Hide resolved
internal/confmapprovider/discovery/testdata/config.d/properties.discovery.yaml
Show resolved
Hide resolved
9073abb
to
079b62b
Compare
6caf10f
to
efc86c3
Compare
efc86c3
to
e7fa477
Compare
These changes add the ability to specify discovery properties in a single
config.d/properties.discovery.yaml
file that are merged w/ env/cli set properties.edit: these changes also fix a bug I introduced where
configDirRootRegex
was using a group in a range exclusion.