-
Notifications
You must be signed in to change notification settings - Fork 15
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
Create an example of federating with a google service account #36
Comments
I think that we can use Something like: xchg := sts.New("https://octo-sts.dev", "does-not-matter", sts.WithScope("wolfi-dev/os"), sts.WithIdentity("blah"))
...
ts, err := idtoken.NewTokenSource(ctx, "octo-sts.dev")
token, err := ts.Token()
res, err := xchg.Exchange(ctx, token)
// Use res.Token @cpanato it'd be great to try this out in the @rawlingsj you mentioned that lifecycle was using PATs, so maybe that's another place we could pilot this with repo-level grants? |
I confirmed that we can use See the code here: https://github.com/chainguard-dev/mattmoor-actions/blob/dd6a460c85933d8eb21e5f8e18cd98c6d2e69a92/main.go#L17-L27 |
I will implement that I need to know how the org one to access any repo will work, I am asking that because the service that takes care of the release notes can be installed for any repo, or we will define per repo as well? |
@cpanato if you put the policy into |
to close this ticket, do you want a code example in the repo? |
I think we should have it somewhere public, but I don't have any great ideas for where. |
i would say here, but this is private, maybe in the action repo for the octo-sts |
We should add token revocation to the sample, e.g. #92 |
... using the
chainguard.dev/sdk
client!The text was updated successfully, but these errors were encountered: