Closed antaflos closed 9 years ago
perhaps a better fix would be to use the apt/yum repositories?
Not, it would not. The package name issue would be the same (or possibly even worse), regardless of where the .deb or .rpm file was downloaded from.
well, you haven't seen my fix yet :P
This is already open as #140. I have a fix we we're working on because both the rpm names and package names change to include gitlab-ce.
@antaflos https://github.com/spuder/puppet-gitlab/compare/master...ahuffman:issue_140. Check out my proposed changes there. It fixes the gitlab and gitlab-ce issue as well as the default package name changes when using the gitlab_branch param.
Closing as duplicate of #140
The packages are now no longer named "gitlab" but "gitlab-ce" or "gitlab-ee". See https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/CHANGELOG.md for confirmation.
This breaks idempotency and Puppet (re)installs Gitlab on every run, because it doesn't find the expected package installed:
Puppet calls
/usr/bin/dpkg-query -W --showformat '${Status} ${Package} ${Version}\n' gitlab
to find the package and its status and version, and this command fails because the package is now named "gitlab-ce" and not "gitlab".Unfortunately I have no immediately great idea how to work around this problem, other than relying on parsing the value of
gitlab::gitlab_branch
and/orgitlab::gitlab_download_link
. As in something like this:I find changing the package name to be a really bad move on GitLab B.V.'s part, especially for a supposedly backwards-compatible feature release.