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

data dir changes in gitlab 9 #137

Closed
logicminds opened this issue Jun 9, 2017 · 2 comments
Closed

data dir changes in gitlab 9 #137

logicminds opened this issue Jun 9, 2017 · 2 comments
Labels
enhancement New feature or request

Comments

@logicminds
Copy link
Contributor

I believe gitlab changed the hash for data dirs again in 9.0. So I think we will need to update the code here. This is additional path attribute with the hash.

Not sure if legacy configs will work or if the path key is required if a path is provided instead of a hash.

Assuming the extra hash is for further configurations when using nfs, cephfs.

https://github.com/vshn/puppet-gitlab/blob/master/manifests/config.pp#L18

git_data_dirs({
  "default" => { "path" => "/var/opt/gitlab/git-data" },
  "nfs" => { "path" => "/mnt/nfs/git-data" },
  "cephfs" => { "path" => "/mnt/cephfs/git-data" }
})

ref: https://docs.gitlab.com/ce/administration/repository_storage_paths.html

@tobru
Copy link
Contributor

tobru commented Jun 9, 2017

Would you mind to create a PR for this change? Would be great!

@juniorsysadmin juniorsysadmin added the enhancement New feature or request label Jan 29, 2018
@LongLiveCHIEF
Copy link
Contributor

I've confirmed with Gitlab support that the legacy formatting is still supported. they had a discrepancy in their docs vs their template file, and I have an issue logged to fix this: https://gitlab.com/gitlab-org/gitlab-ee/issues/4040.

Since our existing template will create both formats successfully, no changes are needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants