• DJ Mountney's avatar
    Change the way we do the rails-secret handling · 4e4d379b
    DJ Mountney authored
    Have the secrets generator always do an apply for rails secrets
    But have it first populate the variables using any existing secret data
    it finds
    
    This allows us to generate secrets for new keys added in new gitlab
    versions, while still respecting/retaining any existing key values.
    4e4d379b
Name
Last commit
Last update
.gitlab/issue_templates Loading commit data...
bin Loading commit data...
changelogs/unreleased Loading commit data...
charts Loading commit data...
dependencies_io Loading commit data...
doc Loading commit data...
examples Loading commit data...
scripts Loading commit data...
spec Loading commit data...
templates Loading commit data...
.dockerignore Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
.helmignore Loading commit data...
CHANGELOG.md Loading commit data...
CONTRIBUTING.md Loading commit data...
Chart.yaml Loading commit data...
Dangerfile Loading commit data...
Gemfile Loading commit data...
Gemfile.lock Loading commit data...
LICENSE.md Loading commit data...
README.md Loading commit data...
Rakefile Loading commit data...
dependencies.yml Loading commit data...
requirements.yaml Loading commit data...
values.yaml Loading commit data...