-
Notifications
You must be signed in to change notification settings - Fork 291
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
Secrets consistency for the chart #1016
Conversation
2d9a3ce
to
b66463f
Compare
At first sight, suggestions make sense to me. @iskhakov, would you take a look? |
b44ac2f
to
ad738a1
Compare
@iskhakov Friendly ping |
Ac |
ad738a1
to
ae05031
Compare
ae05031
to
76e590c
Compare
Can someone take a look, please? |
76e590c
to
d2e0a41
Compare
Is it a common abbreviation? I wonder what it means in this context :) |
2db0aeb
to
d8d3a5a
Compare
@Matvey-Kuk @iskhakov Can you please assign this to someone? |
d8d3a5a
to
b99b536
Compare
b99b536
to
d182e71
Compare
Closed accidentally by pushing a version with incomplete rebase |
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
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.
waiting for changes to pass tests
cb3ba35
to
ad3cebf
Compare
I have doubts about TWILIO_ACCOUNT_SID. IMO it should reside in existingSecret if such exists (as being a part of credentials). |
269b402
to
d8f93e3
Compare
@iskhakov Can you please approve the workflows? Note, that due to a single file accidental change (despite the later reversal) a bunch of unnecessary tests were triggered. Not sure if it is possible to remove them, or we should just run the unnecessary tests. |
d8f93e3
to
8cddc9c
Compare
@iskhakov Please, re-approve the workflows |
f409dc9
to
55462d7
Compare
- Enabling existing secrets for external MySQL and Redis - Tolerate existing secrets for bundled charts. - README.md: secrets handling explained. - Fixed multiple bugs where missing required field was replaced with default instead of failing. - PHONE_NOTIFICATIONS_LIMIT was on the wrong level: it was not set if existingSecret was true. Next are the cosmetic changes. They improve chart consistency, e.g. prevent generation of multiple new lines in certain cases: - Common approach to spaces trimming. This typically allows curly blocks and actual strings indentation and nice `nindent` usage: - Two curly blocks should not trim the same space. I.e. "{{ ... -}} {{- ... }}" shouldn't happen. - Template generates either single line or multiline string. In both cases, no new line appears on both sides of the output string. So we delete unnecessary new lines inside and at the end of string with "trim-to-left" (`{{-` ) and the leading new line using "trim-to-right" (`-}}`). Note that trimming both leading and trailing new line is not always easily possible: Masterminds/sprig#357 Example. ``` {{- define "mytemplate" -}} {{ if someBoolean -}} {{ .Value.some }} {{- else -}} some string {{- end }} {{- end }} ``` - `template` replaced with `include`. It is often recommended to use `include` by default, as it allows pipelining.
55462d7
to
293352f
Compare
I've fixed the tests. Everything seems to run fine in my forked workflow, except for e2e tests which are slow to be picked up by workers: workflow |
Next are the cosmetic changes. They improve chart consistency, e.g. prevent generation of multiple new lines in certain cases:
Common approach to spaces trimming. This typically allows curly blocks and actual strings indentation and nice
nindent
usage:Two curly blocks should not trim the same space. I.e. "{{ ... -}} {{- ... }}" shouldn't happen.
Template generates either single line or multiline string. In both cases, no new line appears on both sides of the output string. So we delete unnecessary new lines inside and at the end of string with "trim-to-left" (
{{-
) and the leading new line using "trim-to-right" (-}}
).Note that trimming both leading and trailing new line is not always easily possible: Function similar to nindent but ignoring content's initial new line. Masterminds/sprig#357
Example.
template
replaced withinclude
. It is often recommended to useinclude
by default, as it allows pipelining.Checklist
CHANGELOG.md
updated