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#version-numbers On Mon, Nov 25, 2019 at 9:47 AM Jonathan Lebon <[email protected]> wrote: > > From: Jonathan Lebon <[email protected]> > > FCOS is now rebased to f31. Bump the signing key accordingly. > > Signed-off-by: Jonathan Lebon <[email protected]> > --- > 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 > _______________________________________________ infrastructure mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
