Describe the issue Update the stable IoT signing keys from F-37 -> F38 on sigul for signing stable release
When do you need this? (YYYY/MM/DD) Now
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
I guess this is:
[consumer_config.ostree_refs."fedora/stable/x86_64/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/" key = "{{ (env == 'production')|ternary('fedora-37', 'testkey') }}" [consumer_config.ostree_refs."fedora/stable/aarch64/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/"
moving to fedora-38 key?
When do you need this by? Can we do it after freeze? Or you need it for release?
I guess this is: [consumer_config.ostree_refs."fedora/stable/x86_64/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/" key = "{{ (env == 'production')|ternary('fedora-37', 'testkey') }}" [consumer_config.ostree_refs."fedora/stable/aarch64/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/" moving to fedora-38 key?
That's correct.
We need it for release to move the tree over to stable from devel (aka branched)
Metadata Update from @phsmoura: - Issue tagged with: high-gain, medium-trouble, ops
Done! Please let us know if you need anything further.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.