tailscale / tailscale/aperture-cli
Workload Identity Federation for Gemini Enterprise Agent Platform
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 74
- Forks
- 13
- Avg merge
- 1h
- Merged PRs (30d)
- 7
Description
I'm not sure this is the right place to open the issue, so feel free to redirect me elsewhere or move it yourself...
I was setting up Aperture for the Gemini Enterprise Agent Platform, and see it relies on a JSON key file credential. Our org restricts the creation of keys by policy, highly encouraging us to use Workload Identity Federation instead. Is it possible already for Aperture to use WIF, and if so how would I set it up? If not, is that a feature you would consider implementing?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Aperture setup described in the linked Gemini Enterprise Agent Platform documentation and trace how its JSON key file credential is supplied. Determine whether the current integration accepts Workload Identity Federation; if not, define the required configuration and authentication flow. Done means a supported WIF setup is documented or the feature scope is clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100