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

feat(configmap): Add possibility to provide extra vars in configmap. #47

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

abennani82
Copy link

Hi,
PR de fix #45 as requested.
Thanks for review
Regards

@abennani82
Copy link
Author

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?

Copy link
Owner

@a5r0n a5r0n left a 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 }}
Copy link
Owner

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

Suggested change
{{- with .Values.extraEnvs }}
{{- with .Values.n8n.extraEnvs }}

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check this @abennani82

@a5r0n
Copy link
Owner

a5r0n commented Sep 6, 2024

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 🙏🏻

@abennani82
Copy link
Author

abennani82 commented Sep 9, 2024 via email

Copy link
Owner

@a5r0n a5r0n left a 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?

@abennani82
Copy link
Author

abennani82 commented Sep 10, 2024 via email

@abennani82
Copy link
Author

Resources deleted

@abennani82
Copy link
Author

Hi
I’m not aware about pr GitHub process. Have y get changes from my pr ?

@a5r0n
Copy link
Owner

a5r0n commented Dec 19, 2024

@abennani82 you also deleted the charts them self, not just from the git commit..

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

Successfully merging this pull request may close these issues.

Use extra vars for deployment
2 participants