-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat(configmap): Add possibility to provide extra vars in configmap. #47
base: main
Are you sure you want to change the base?
Conversation
Can i add the ability to provide external secret ( for N8N_ENCRYPTION_KEY for example) to this PR or it has to be in a separate one? |
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.
chart dependencies should be updated on different PR, (actually renovate will do)
DB_LOGGING_OPTIONS: {{ .Values.n8n.db_logging_options | default "all" | quote }} | ||
{{- with .Values.extraEnvs }} |
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'd like to keep things orgainzied, all n8n relatead config should be inside .Values.n8n block
{{- with .Values.extraEnvs }} | |
{{- with .Values.n8n.extraEnvs }} |
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.
Please check this @abennani82
separate one please 🙏🏻 |
Ok.
I’m waiting the validation of the first PR to send u the second one.
Aissam BENNANI
Le ven. 6 sept. 2024 à 16:31, a5r0n ***@***.***> a écrit :
… Can i add the ability to provide external secret ( for N8N_ENCRYPTION_KEY
for example) to this PR or it has to be in a separate one?
separate one please 🙏🏻
—
Reply to this email directly, view it on GitHub
<#47 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKCQC5XBHUDMSD5BKO54WVLZVG4F5AVCNFSM6AAAAABNYVCYMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUGE4TEMRVHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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.
Can you remove the Chart.{yaml/lock} and dependent charts from this PR?
I thaught it was already there.
I fix that
Aissam BENNANI
Le lun. 9 sept. 2024 à 21:47, a5r0n ***@***.***> a écrit :
… ***@***.**** commented on this pull request.
Can you remove the Chart.{yaml/lock} and dependent charts from this PR?
—
Reply to this email directly, view it on GitHub
<#47 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKCQC5SCOBZIHR3MYAGUAWDZVX3NFAVCNFSM6AAAAABNYVCYMSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEOJQHAYTCNJXGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Resources deleted |
Hi |
@abennani82 you also deleted the charts them self, not just from the git commit.. |
Hi,
PR de fix #45 as requested.
Thanks for review
Regards