miabbott reported a new issue against the project: `atomic-wg` that you are following: `` A common problem that users hit when a new major release lands is having to manually configure a new remote or modify an existing remote to use the new major release GPG key. This is exacerbated now that we have a unified repo for all of our refs.
A solution pointed out in the [upstream ostree issue](https://github.com/ostreedev/ostree/issues/773#issuecomment-380773355) is to use the `ostree remote gpg-import` functionality to make the recent keys available to the remote.
Would it be possible to change how we produce the cloud-images/AMIs/ISOs so that the pre-configured remote uses this method to make all the recent keys available?
``` # ostree remote add fedora-atomic https://dl.fedoraproject.org/atomic/repo/ # cat /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-{27,28,29}-primary |ostree remote gpg-import --stdin fedora-atomic ``` ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/461