A better way to enable add-on Terraform for different cloud providers?

[zzxwill]

vela addon enable terraform <CloudProvider> -<CredentialKey>=<CredentialValue> ...

By default, is alibaba, without setting it, terraform controller chart will be installed. A secret and a Provider object will be created.

Then if the platform team wants to provision AWS, he/she runs the command.

vela addon enable terraform was -AWS_ACCESS_KEY_ID=xxx -AWS_SECRET_ACCESS_KEY=yyy.

The terraform controller will NOT be installed again. Only the provider for AWS will created.

[wonderflow]

vela secret my-sec  AWS_ACCESS_KEY_ID=xxx -AWS_SECRET_ACCESS_KEY=yyy
vela addon enable terraform-provider-aws --secret my-sec

[zzxwill]

The better solution from @wonderflow
vela addon enable terraform-provider-aws --AWS_ACCESS_KEY_ID=xxx -AWS_SECRET_ACCESS_KEY=yyy

[chivalryq]

vela addon enable terraform-provider-aws --secret 'AWS_ACCESS_KEY_ID=xxx -AWS_SECRET_ACCESS_KEY=yyy'

I suggest vela addon enable terraform/provider-alicloud, which indicates the hierarchical relationship between terraform and provider addons.

It would be an logical represent and implemented by replace “/” with “-”.

[wonderflow]

@chivalryq cool, it's good

[zzxwill]

Great, let's use vela addon enable terraform/provider-aws --AWS_ACCESS_KEY_ID=xxx -AWS_SECRET_ACCESS_KEY=yyy