Skip to content

Backport 1.7.x: Update Agent Auth with GCP to use new SignJWT endpoint (#11473)#11508

Merged
austingebauer merged 3 commits intorelease/1.7.xfrom
backport-pr-11473-1.7.x
May 6, 2021
Merged

Backport 1.7.x: Update Agent Auth with GCP to use new SignJWT endpoint (#11473)#11508
austingebauer merged 3 commits intorelease/1.7.xfrom
backport-pr-11473-1.7.x

Conversation

@catsby
Copy link
Contributor

@catsby catsby commented Apr 30, 2021

Backports #11473 to the 1.7.x branch:


Updates Vault Agent's GCP auth to use GCP's IAM Service Account Credential endpoint for signing JWTs, as the IAM endpoint versions are deprecated. See https://cloud.google.com/iam/docs/migrating-to-credentials-api for more information on the deprecation and migration.

See also for more backstory:

* Update Agent Auth with GCP to use new SignJWT endpoint

* use iamcredentials name instead of renaming the package on import

* add changelog

* Update changelog/11473.txt

Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>

Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>
@catsby catsby modified the milestones: 1.7.1, 1.7.2 Apr 30, 2021
@vercel vercel bot temporarily deployed to Preview – vault-storybook May 6, 2021 20:03 Inactive
@austingebauer austingebauer merged commit 3ad0987 into release/1.7.x May 6, 2021
@austingebauer austingebauer deleted the backport-pr-11473-1.7.x branch May 6, 2021 20:32
pull bot pushed a commit to Zezo-Ai/vault that referenced this pull request Dec 22, 2025
…#11508) (hashicorp#11533)

Update the base images for all scenarios:

- RHEL: upgrade base image for 10 to 10.1
- RHEL: upgrade base image for 9 to 9.7
- SLES: upgrade base image for 15 to 15.7
- SLES: add SLES 16.0 to the matrix
- OpenSUSE: remove OpenSUSE Leap from the matrix

I ended up removing OpenSUSE because the images that we were on were rarely updated and that resulted in very slow scenarios because of package upgrades. Also, despite the latest release being in October I didn't find any public cloud images produced for the new version of Leap. We can consider adding it back later but I'm comfortable just leaving SLES 15 and 16 in there for that test coverage.

I also ended up fixing a bug in our integration host setup where we'd provision three nodes instead of one. That ought to result in many fewer instance provisions per scenario. I also had to make a few small tweaks in how we detected whether or not SELinux is enabled, as the prior implementation did not work for SLES 16.

Signed-off-by: Ryan Cragun <me@ryan.ec>
Co-authored-by: Ryan Cragun <me@ryan.ec>
tsaarni pushed a commit to Nordix/vault that referenced this pull request Jan 8, 2026
…#11508) (hashicorp#11537) (hashicorp#11539)

Update the base images for all scenarios:

- RHEL: upgrade base image for 10 to 10.1
- RHEL: upgrade base image for 9 to 9.7
- SLES: upgrade base image for 15 to 15.7
- SLES: add SLES 16.0 to the matrix
- OpenSUSE: remove OpenSUSE Leap from the matrix

I ended up removing OpenSUSE because the images that we were on were rarely updated and that resulted in very slow scenarios because of package upgrades. Also, despite the latest release being in October I didn't find any public cloud images produced for the new version of Leap. We can consider adding it back later but I'm comfortable just leaving SLES 15 and 16 in there for that test coverage.

I also ended up fixing a bug in our integration host setup where we'd provision three nodes instead of one. That ought to result in many fewer instance provisions per scenario. I also had to make a few small tweaks in how we detected whether or not SELinux is enabled, as the prior implementation did not work for SLES 16.

Signed-off-by: Ryan Cragun <me@ryan.ec>
Co-authored-by: Ryan Cragun <me@ryan.ec>
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.

4 participants