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.

Sign up for GitHub

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

Jump to bottom

Use one source of truth for variables and secretes within all deployment stages #115

Open
3 tasks
Tracked by #113
turnerrainer opened this issue Mar 28, 2024 · 0 comments · Fixed by #117
Open
3 tasks
Tracked by #113

Use one source of truth for variables and secretes within all deployment stages #115

turnerrainer opened this issue Mar 28, 2024 · 0 comments · Fixed by #117
Assignees
@1AhmedYasser
Labels
v2.0
Milestone
NoOps 1.0.0 code ...

Comments

@turnerrainer
Copy link
Contributor

turnerrainer commented Mar 28, 2024 •
edited

AS AN Architect
I WANT only one source of truth to be used for variables and secretes within all deployment stages
SO THAT there wouldn't be any misconfiguration due to the same variable used in different locations and not being updated accordingly

Acceptance Criteria

  • Have separate sources of truth for every component and module
  • Define all required variables in Helm values.yaml
  • Import all applicable variables in Helm's deployment YAMLs from Helm values.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@1AhmedYasser 1AhmedYasser

Labels
v2.0
Projects
Bürokratt Sprint
Status: Done
Milestone
NoOps 1.0.0 code freeze
Development

Successfully merging a pull request may close this issue.

Source of truth for variables and secretes 1AhmedYasser/NoOps
2 participants
@1AhmedYasser @turnerrainer