-
Notifications
You must be signed in to change notification settings - Fork 4
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
[CNFT1-3307] Adds event search feature flags #588
Conversation
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.
See comment. Default values may be blank by using "| quote" notation
'--nbs.ui.features.patient.add.extended.enabled={{ (((((.Values).ui).patient).add).extended).enabled | default "false" }}', | ||
'--nbs.ui.settings.smarty.key={{ .Values.ui.smarty.key }}', | ||
'--nbs.ui.settings.analytics.key={{ .Values.ui.analytics.key }}' | ||
'--nbs.ui.features.search.events.enabled={{ ((((.Values).ui).search).events).enabled }}', |
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.
There should be a default value for new and existing inputs that are required in values.yaml (the de facto release values file). Otherwise deployments may break in other environments.
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.
Made sure that boolean values have a default so that the service starts as expected. Will look into making blank values for boolean valid in the future
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.
Looks good. New optional inputs have defaults and older required values are as before.
Adds configurable feature flags for;
All three flags have been enabled for the INT1 environment. These changes can be merged ahead of the
modernization-api
changes that use these values.