I'm asking because in the Ansible example in https://github.com/deislabs/bundles/blob/master/ansiblebase/... I see AZURE_TENANT AZURE_CLIENT_ID AZURE_SECRET AZURE_SUBSCRIPTION_ID but nothing for other clouds.
Would you have to add configuration for every cloud you have to support?
It seems that in this context cloud agnostic means any cloud can be supported.
I'm interested in application portability [0]. To do this with CNAB you need to add every cloud to the bundle. This is contrast to something like Crossplane [1] that intents to support multi-cloud with a single specification.
0. https://medium.com/gitlab-magazine/multi-cloud-maturity-mode...
I get the specification is cloud agnostic. But it looks like the developer needs to write the underlying code to provision and maintain the application on the various clouds. It feels like a too thin abstraction. And it seems pretty leaky currently; the examples all have hard and specific requirements e.g. Azure, k8s etc.
What am I missing? Is the idea that we will create tooling to automatically create the provisioning and maintenance code?