-
Task
-
Resolution: Done
-
Major
-
None
-
False
-
-
False
-
ANSTRAT-411 - Content Signing
Problem Description: pulp_ansible will remove the `keyring` from repositories and replace it with a `gpgkey` field to hold the plain text of the public key instead of the path to a keyring on filesystem.
Where the change will affect:
Right now on Hub the `keyring` is set by running `django-admin set-repo-keyring` management command , which is set to run on every deployment via container entrypoint.
On integration tests the `keyring` is requested on repo endpoint to decide if test is skipped or not.
What are the actions needed to accommodate the change:
When upgrading to pulp_ansible version containing https://github.com/pulp/pulp_ansible/pull/1088/files
- Change the `set-repo-keyring` command to read the keyring on filesystem and store its plain text public key on the repo.gpgkey instead of the path on `keyring` field.
- Set `settings.REQUIRE_SIGNATURE_VERIFICATION_ON_UPLOAD` (or so) new setting that will come with that PR
- Update documentation on upstream mentioning that the repo now takes a plain text public key instead of the path for a keyring
- relates to
-
AAH-1821 upgrade to pulp_ansible 0.15
- Closed
- mentioned on