jenkinsci / jenkinsci/google-compute-engine-plugin
Do not require additional configuration to pick controller's authn - use providers default chain
Open
- Dominant language
- Java
- Stars
- 58
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Description
Currently even for controller running in GKE and GCE — plugin is requiring to mention explicity,
```
- googleRobotMetadata:
id: gcp
projectId:
```
same in the UI just putting the project name.
The SDKs default chain would pick the project and the identity of the GKE deploy or GCE vm as the authn of the controller.
Contributor guide
Assessment
This issue has not been assessed yet.