On that topic, one thing we'd like to do in the future is making RoboSignatory smarter so that it can automatically select the right release key based on the FCOS version string[1]. The versioning scheme is available at [2].
[1] https://github.com/coreos/fedora-coreos-tracker/issues/296 [2] https://github.com/coreos/fedora-coreos-tracker/blob/master/Design.md#versio...
On Mon, Nov 25, 2019 at 9:47 AM Jonathan Lebon jlebon@redhat.com wrote:
From: Jonathan Lebon jonathan@jlebon.com
FCOS is now rebased to f31. Bump the signing key accordingly.
Signed-off-by: Jonathan Lebon jonathan@jlebon.com
roles/robosignatory/templates/robosignatory.toml.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/robosignatory/templates/robosignatory.toml.j2 b/roles/robosignatory/templates/robosignatory.toml.j2 index 8126648c9..520ec72ee 100644 --- a/roles/robosignatory/templates/robosignatory.toml.j2 +++ b/roles/robosignatory/templates/robosignatory.toml.j2 @@ -476,7 +476,7 @@ handlers = ["console"]
[consumer_config.coreos] bucket = "fcos-builds"
- key = "{{ (env == 'production')|ternary('fedora-30', 'testkey') }}"
key = "{{ (env == 'production')|ternary('fedora-31', 'testkey') }}"
[consumer_config.coreos.aws] access_key = "{{ fcos_builds_releng_aws_access_id }}"
-- 2.23.0