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

New GitLab GPG Keys #333

Closed
yakatz opened this issue Mar 31, 2020 · 3 comments
Closed

New GitLab GPG Keys #333

yakatz opened this issue Mar 31, 2020 · 3 comments

Comments

@yakatz
Copy link
Contributor

yakatz commented Mar 31, 2020

GitLab has announced they are changing their GPG keys. It is not clear to me exactly what needs to be done in this module to support that. I don';t know enough about how Yum keys work. Changing the Debian keys looks to be straightforward, but the change needs to be made on April 6.

Announcement: https://about.gitlab.com/releases/2020/03/30/gpg-key-for-gitlab-package-repositories-metadata-changing/

Documentation: https://docs.gitlab.com/omnibus/update/package_signatures#package-repository-metadata-signing-keys

@dnsmichi
Copy link

dnsmichi commented Apr 1, 2020

Thanks for the heads up. I was about to create a PR but then saw that #331 is already there.

In order to avoid dependency on a release, you should be able fetch and install the new key with a custom repository_configuration setting shown in https://github.com/voxpupuli/puppet-gitlab#custom-repository--package-configuraiton-example

class { 'gitlab':
  # ...
  repository_configuration => {
    'apt::source' => {
      'gitlab_official_ce' => {
        'comment' => 'Official repository for GitLab Omnibus',
        'location' => 'https://packages.gitlab.com/gitlab/gitlab-ce/debian',
        'key' => {
          'id' => 'F6403F6544A38863DAA0B6E03F01618A51312F3F',
          'source' => 'https://gitlab-org.gitlab.io/omnibus-gitlab/gitlab_new_gpg.key'
        }
      },
    }
  }
}

Once you roll that out, the new GPG key is fetched and at a later point when this module gets a release bump you'll change back to the official key defaults with removing this setting. Or you change the URL for the source entry.

@baurmatt
Copy link
Contributor

baurmatt commented Apr 8, 2020

This was fixed by #331 and released with 5.0.0

@baurmatt baurmatt closed this as completed Apr 8, 2020
@dnsmichi
Copy link

dnsmichi commented Apr 8, 2020

Thanks for the fast update & release, really appreciate it ❤️

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

3 participants