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
Allow users to migrate hardware templates by invoking the hardware template migration API.
a user, should be able to modify the deployment_template_id field, and migrate their deployment to a different hw template.
deployment_template_id
data "ec_stack" "latest" { version_regex = "7.*" region = "eu-west-1" } resource "ec_deployment" "staging" { name = "omer-test" region = "eu-west-1" version = data.ec_stack.latest.version deployment_template_id = "aws-storage-optimized" # -> changing to "aws-compute-optimized" for example. elasticsearch { topology { id = "hot_content" size = "1g" zone_count = 3 } topology { id = "warm" size = "2g" zone_count = 2 } } kibana { topology { size = "1g" zone_count = 1 } } }
The text was updated successfully, but these errors were encountered:
https://github.com/elastic/sdh-control-plane/issues/1023#issuecomment-1201872409 indicates that this enhancement might have dependencies on the framework migration. @Kushmaro we'll want to confirm whether this is the case before committing to 0.5.0
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Allow users to migrate hardware templates by invoking the hardware template migration API.
a user, should be able to modify the
deployment_template_id
field, and migrate their deployment to a different hw template.The text was updated successfully, but these errors were encountered: