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

gitlab-secrets.json is destroyed and recreated on every puppet run #87

Closed
seefood opened this issue Aug 10, 2016 · 1 comment
Closed

Comments

@seefood
Copy link

seefood commented Aug 10, 2016

Sample dump at http://pastebin.com/v3J98Az2

Basically, the http secret, cert and internal key, plus all the mattermost salts and keys, all get removed with every puppet run and immediately new ones are generated and added by the reconfigure, which was triggered by the fact the file was edited. this seems to me like a serious bug, the entire omnibus should not need to rerun and restart on every run.
Also, does that mean mattermost is getting installed? should I be able to access it? it's not linked in the gitlab UI and I don't see any service that looks like it's related getting started.

@tobru
Copy link
Contributor

tobru commented Aug 10, 2016

The secrets in the gitlab::secrets hash must be in the exact same order as in the JSON file as gitlab-ctl rewrites the file on every run. You can also leave the parameter blank, the file is not touched then. See https://github.com/vshn/puppet-gitlab/blob/master/manifests/config.pp#L101
Regarding Mattermost: Please consult the Gitlab documentation for that: http://docs.gitlab.com/omnibus/gitlab-mattermost/ It is fully supported by this Puppet module.

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

No branches or pull requests

2 participants