Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

signingscript: autograph gcp migration step 2: test against gcp prod #1099

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

bhearsum
Copy link
Contributor

@bhearsum bhearsum commented Dec 3, 2024

This patch adds another set of new formats that point at Autograph GCP prod. These entries contain equivalents for all current production formats, and use the exact same credentials the existing production formats. Where they differ are:

  • Different formats (so we can opt into them)
  • Different autograph URL
  • Ensure we use explicit keyids everywhere

Note that this patch landing and being deployed should not end up changing how we sign anything on its own, it will merely make gcp prod available to dev and fake-prod workers.

This patch adds another set of new formats that point at Autograph GCP prod. These entries contain equivalents for all current production formats, and use the exact same credentials the existing production formats. Where they differ are:
* Different formats (so we can opt into them)
* Different autograph URL
* Ensure we use explicit keyids everywhere
@bhearsum
Copy link
Contributor Author

This has been tested as thoroughly as possible. I covered:

I was unable to test app services and glean due to not having anything except prod worker pools set up for them. (I don't think this is worth fixing as a blocker here, but I could be convinced otherwise.)

I was also unable to test the mobile trust domain via staging-reference-browser due to it not being in projects.yml (being addressed in mozilla-releng/fxci-config#259), and I suspect that it is also does not have the firefoxci app installed. Again, I don't think this is worth blocking this on, but I could be convinced otherwise.

@bhearsum bhearsum marked this pull request as ready for review January 14, 2025 18:29
@bhearsum bhearsum requested a review from jcristau January 14, 2025 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant