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

NOTES.txt has a bad substring causing the templates to not render #94

Closed
sushil-rxr opened this issue Nov 14, 2020 · 3 comments
Closed

Comments

@sushil-rxr
Copy link

The NOTES.txt has an entry such as "The requested connection scaling tier for this deployment is: max {{ substr 4 10 .Values.solace.size }} connections." This substring logic is failing when we use the strings such as prod1k etc. for the solace.size parameter value.

@bczoma
Copy link
Collaborator

bczoma commented Nov 16, 2020

Hi sushil-rxr, thanks for raising I'll look into this for the next update

@bczoma
Copy link
Collaborator

bczoma commented Nov 30, 2020

Hi, I have just tried with solace.size=prod1k and getting:

== Performance and resource requirements ==
The requested connection scaling tier for this deployment is: max 1k connections.

Wondering if you are getting the same and if so what the issue with above is.

@bczoma
Copy link
Collaborator

bczoma commented Dec 18, 2020

@sushil-rxr - kindly provide an update if this is still an issue

PhilippeKhalife pushed a commit that referenced this issue Jan 27, 2021
* Added support to configure server certificates for TLS
* Improved logic to set and log pod active labels as part of readiness check
* Updated names and file locations for readiness check related files to align with long-term broker file system strategy
* Renamed internal script setup-config-sync to startup-broker
* Added more default exposed ports, unified port names
* Added automation coverage for TLS configuration
* Fixed reference to Helm hub
* Updated chart version to 2.4

Closes  issues #87, #92, #94, #98
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants