f7f42cf345
In `deploy`, if the previous deployment failed, we delete/cleanup all the objects related to the release, including secrets. The problem is that if we create the root password before that, it will be then recreated during the deploy with a random value! By creatigng the secret just before actually deplying a new release, we ensure that it won't be overriden. Signed-off-by: Rémy Coutable <remy@rymai.me> |
||
|---|---|---|
| .. | ||
| frontend | ||
| review_apps | ||
| build_assets_image | ||
| create_mysql_user.sh | ||
| create_postgres_user.sh | ||
| detect-new-flaky-examples | ||
| gitaly-test-build | ||
| gitaly-test-spawn | ||
| gitaly_test.rb | ||
| lint-changelog-yaml | ||
| lint-conflicts.sh | ||
| lint-doc.sh | ||
| lint-rugged | ||
| merge-reports | ||
| merge-simplecov | ||
| no-ee-check | ||
| prepare_build.sh | ||
| prune-old-flaky-specs | ||
| rails5-gemfile-lock-check | ||
| schema_changed.sh | ||
| security-harness | ||
| static-analysis | ||
| sync-reports | ||
| trigger-build | ||
| trigger-build-docs | ||
| utils.sh | ||