Conversation
As long is this command is in private beta, it remains hidden.
SimonBarendse
left a comment
There was a problem hiding this comment.
Looks mostly good 👍
Just found one piece of logic that isn't clear to me yet (see comment), could you clarify this for me?
This PR mentions "private beta" status and hides the command in the help text.
Have we already considered how we want to communicate the "private beta" state to the user? I believe the most important aspect of this is being clear about what users can expect with regards to stability and backwards-compatibility of the feature.
You've already addressed this state in this PR's description. Do we want to expand that message with the expectations a user can have of "private beta" features?
When the PR follows its way into production, we can continue to share this message along the way, for example in:
- In this PRs description
- In release notes
- In documentation (including help texts)
- When using it (e.g. print a warning on stderr)
If we haven't formed a strategy around this yet: shall we have a quick brainstorm?
It is still in private beta, listing it would be confusing.

Adds a new credential type for GCP Service Account, which allows a service running on GCP to use keyless authentication.
Introduces a new (currently hidden)
secrethub service gcpsubcommand and allowsgcpas an Identity Provider.Please note: this feature starts in private beta. By default, it will not be enabled on your namespace. If you want to give it a try, reach out to us at support@secrethub.io.