Allow passing kyma configuration ( in form of json file ) when calling kyma provision command:
[x] user should be able to pass a config json file that is compliant with the provisioning params schema from KEB (see attachments), ie kyma provision --parameters=kyma.json
[x] the parameters should be optional. (Mandatory name and region could be also provided as dedicated command options
[x] parameters provided as flags should have precedence over potentially overlapping parameters from json (--name and --region )
[x] paramaters json file that works when used in BTP Cockpit of via BTP CLI (see attachments) should also work with Kyma CLI
Reasons
Kyma Environment Broker supports passing additional parameters when creating/updating kyma environment.
Kyma CLI provision command should allow passing the config.json file to allow configuring OIDC providers.
Description
Allow passing kyma configuration ( in form of json file ) when calling
kyma provisioncommand:kyma provision --parameters=kyma.jsonnameandregioncould be also provided as dedicated command options--nameand--region)Reasons
Kyma Environment Broker supports passing additional parameters when creating/updating kyma environment. Kyma CLI provision command should allow passing the config.json file to allow configuring OIDC providers.
Attachments params-schema.json
BTP Cockpit Screenshot:
sample provisioning via BTP CLI:
btp create accounts/environment-instance --display-name fooo --environment kyma --service kymaruntime --plan trial --parameters config.json