-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
Comments
|
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 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 |
|
This was fixed by #331 and released with 5.0.0 |
|
Thanks for the fast update & release, really appreciate it ❤️ |
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
The text was updated successfully, but these errors were encountered: