Static/automated API key definition

[zatkowich]

What would you like to be added:

We need a way how to avoid manual API key setup.

Why is this needed:

Well, the reason is a very simple: option for fully automated setup.

[eeshaanSA]

Hey @zatkowich, do you mean automating the creation of piped key?

[zatkowich]

No, I mean what I wrote :) API keys, example scenario:

I have both Control Plane and Piped installed using Helm with GitOps, this is automated.
Now I want to register Piped into Control Plane using TF provider.
I have to go into GUI, create API token and paste it into provider config.
Only then I can continue with registering the Piped in automation process.

So I suggest that either the token could be 'static' - passed into Control Plane deployment or generated on PipeCD side somehow - with some API or any viable way (could be used in initContainer, for example, and secret saved e.g. into Vault).