Is there an open issue addressing this request? If it does, please add a "+1" reaction to the
existing issue, otherwise proceed to step 2.
Describe the feature you are requesting, as well as the possible use case(s) for it.
The feature being requested is to make the configuration of charts customizable and remove any fixed values from the charts. The suggestion is to replace the hardcoded values with configurable variables. For example, instead of using {{ .Release.Name }} in the chart, the proposal is to use {{Values.defaults.msgBrokerProtocol}}://{{ .Release.Name }}-{{msgBrokerUrl}}:{{ .Values.defaults.msgBrokerPort }}. However, this alternative syntax is considered confusing and less readable compared to using {{messageBrokerUrl}}. The suggestion also includes adding a comment with a list of available URLs that can be used.
The possible use case for this feature is to provide flexibility in configuring charts and allowing users to customize values based on their specific requirements. By removing hardcoded values and introducing configurable variables, users can easily adapt the charts to their desired environment without modifying the chart's source code. This enhances reusability and simplifies the process of deploying and managing applications using these charts.
FEATURE REQUEST
Is there an open issue addressing this request? If it does, please add a "+1" reaction to the existing issue, otherwise proceed to step 2.
Describe the feature you are requesting, as well as the possible use case(s) for it.
The feature being requested is to make the configuration of charts customizable and remove any fixed values from the charts. The suggestion is to replace the hardcoded values with configurable variables. For example, instead of using {{ .Release.Name }} in the chart, the proposal is to use {{Values.defaults.msgBrokerProtocol}}://{{ .Release.Name }}-{{msgBrokerUrl}}:{{ .Values.defaults.msgBrokerPort }}. However, this alternative syntax is considered confusing and less readable compared to using {{messageBrokerUrl}}. The suggestion also includes adding a comment with a list of available URLs that can be used.
The possible use case for this feature is to provide flexibility in configuring charts and allowing users to customize values based on their specific requirements. By removing hardcoded values and introducing configurable variables, users can easily adapt the charts to their desired environment without modifying the chart's source code. This enhances reusability and simplifies the process of deploying and managing applications using these charts.
Reference : https://github.com/mainflux/devops/pull/120#issuecomment-1220577900