We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloud_provider
To keep a trace:
For the BE, we need to provide the --usecase and the --cloud-provider to the environment if we want to associate a cloud-provider to an environment.
--usecase
--cloud-provider
cloud-provider
environment
From a naive approach, it looks like this:
cy project create --name my-project --usecase second --cloud-provider google ...
but my second provider defines a cloud_provider: aws so my final env will be associated to google.
second
cloud_provider: aws
google
The goal of this issue, is to be able to fetch the cloud_provider from the stack spec.
stack
GET /organizations/{organization_canonical}/service_catalogs/{service_catalog_ref}/config
can be a good entrypoint for the implementation
The text was updated successfully, but these errors were encountered:
fhacloid
No branches or pull requests
To keep a trace:
For the BE, we need to provide the
--usecase
and the--cloud-provider
to the environment if we want to associate acloud-provider
to anenvironment
.From a naive approach, it looks like this:
but my
second
provider defines acloud_provider: aws
so my final env will be associated togoogle
.The goal of this issue, is to be able to fetch the
cloud_provider
from thestack
spec.can be a good entrypoint for the implementation
The text was updated successfully, but these errors were encountered: