Use btpcli API to craft headless kubeconfig

[kwiatekus]

Description Rework kyma alpha oidc command so that it can communicate with btp backend API (used by btp cli) to download kyma instance's kubeconfig and craft a headless version of it.

Instead of CIS credentials the user should be able to pass BTP accessToken obtained via oidc token request towards subacount trusted custem IAS tenant:

• Replace --credentials-path with --btpAccessToken
• Rename to (or create a new command variant under new name): kyma alpha get access btp

  kyma alpha get access btp --btpAccessToken {accessToken of bot user} --kymaToken {accessToken of bot user} --output 

• Is it possible to move kyma alpha access to kyma alpha get access

  kyma alpha get access --clusterrole --kubeconfig --name string --output --time 

Attachments

• how it is used in demo flow via btp CLI
• how it is used in another POC via btp CLI API server

Reason Better first-time experience when getting initial access.

[kwiatekus]

When using terraform (or tofu), the kubeconfig download URL is already available in the the state files. There is no real value in adding a extra command to download it.. Closing