Open nemonik opened 3 years ago
Current config/
files are little bit older. Some secrets also missing as reported in #2356 ..
I'm trying to sync them to upstream but it takes a time to keep compatibility with customized parameters. If you need it soon, I recommend you to
config/secrets.yml
, assets/runtime/env-default
update_template ${GITLAB_SECTETS_CONFIG}
in assets/runtime/functions
docker-compose.yml
and run your self-built image.Thank you for your reply.
It appears at the moment a restore of a backup works on omnibus without this particular value set.
If this turns out not to be the case I am thankful to have your response to work with.
Y
encrypted_settings_key_base
was introduced starting with 13.7https://docs.gitlab.com/ee/administration/encrypted_configuration.html#encrypted-configuration
The Omnibus Helm chart https://docs.gitlab.com/charts/installation/secrets.html#gitlab-rails-secret handles this secret in this manner. It seems it can be autogenerated, but this may present data migration or restore to Omnibus problems.
How is sameersbn/docker-gitlab handling
encrypted_settings_key_base
? it isn't being set... There is no /etc/gitlab/gitlab-secrets.json as values are passed in as environmental variable...I need to know this in order to migrated a backup out of sameersbn/docker-gitlab to an Omnibus GitLab Helm chart deployment.
No value exists in
/etc/docker-gitlab/runtime/env-defaults
. So, I'm guessing it either never gets set or it is being set and the value held elsewhere. If so how do I determine the present value?Digging around you can generate the
encrypted_settings_key_base
like so as per source installation guidance (https://docs.gitlab.com/ee/administration/encrypted_configuration.html#encrypted-configuration)but it doesn't get written into the
config/secrets.yml
located in/etc/docker-gitlab/runtime/config/gitlabhq/secrets.yml
which your code emplaces as