feat: Add Google Access Token support for GCP actions#39
Conversation
Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot <copilot@github.com>
a745450 to
2aa0266
Compare
Revert to an earlier version of @backstage/backend-plugin-api to maintain compatibility with the current Backstage setup.
|
Nice work on this overall — the feature's useful. The main thing I'd want sorted before merge is how the access token is handled. There are a couple of spots where it can end up persisted, and one option that doesn't actually work. First, the field extension calls both Same thing with the explicit Last one: the I also regenerated |
|
Awesome I'll work on these updates and push em to the branch! |
|
@tdabasinskas take a look at this and let me know what you think. I was able to test in my sandbox and was able to create all 3 resources! 🎆 |
tdabasinskas
left a comment
There was a problem hiding this comment.
Thanks! Appreciate the contribution!
Introduce a Google Access Token field extension for GCP authentication and enable the usage of user OAuth tokens in GCP actions. This enhances flexibility in authentication methods for GCP services.
Please do give this a through review, as I leaned pretty heavy on AI to write this.