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

[Correction] Upgrade fulcios to use of the google privateca api at v1 #252

Merged
merged 6 commits into from
Dec 1, 2021

Conversation

n3wscott
Copy link
Contributor

@n3wscott n3wscott commented Dec 1, 2021

Relands and corrects #218

Signed-off-by: Scott Nichols [email protected]

Summary

We were still on a v1beta1 api for the googleca private ca. This adds a flag to use the v1 of the api. We are still needing to update the cert to v1.

The new flag --gcp_private_ca_version selects v1 by default to allow us to drop the flag when we move to v1 certs and then delete the flag and the v1beta1 codepaths.

Ticket Link

Relates to a checkbox in #191

Release Note

Fulcio now can use the v1 api for google privateca.

ca, err = googlecabeta.NewCertAuthorityService()
version := viper.GetString("gcp_private_ca_version")
switch version {
case "v1":
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the original pr, these where switches and no one caught it...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ooops!

ca, err = googlecabeta.NewCertAuthorityService()
version := viper.GetString("gcp_private_ca_version")
switch version {
case "v1":
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ooops!

@dlorenc dlorenc merged commit 7f42ba5 into sigstore:main Dec 1, 2021
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.

2 participants