You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
resource"spotinst_ocean_aws""ocean_eks" {
...image_id=var.eks_amischeduled_task {
tasks {
is_enabled=truecron_expression=var.spotinst_ami_auto_update_scheduletask_type="amiAutoUpdate"parameters {
ami_auto_update {
apply_roll=trueami_auto_update_cluster_roll {
comment="spot ami auto update"batch_min_healthy_percentage=100batch_size_percentage=20respect_pdb=true
}
minor_version=truepatch=true
}
}
}
}
lifecycle {
ignore_changes=[
image_id# image_id is a dynamic value that is modified by Spotinst. It should only be set initially
]
}
}
Expected Behavior
image_id should not be required when using the AMI auto update feature, as it would conflict with values auto-updated by spot.io.
Actual Behavior
image_id is required
Additional Info
Can you elaborate on how AMI auto update should be used with this terraform provider? It seems like the required image_id will conflict with changes that are done automatically by the AMI auto update feature.
As a temporary workaround we added lifecycle ignore_changes to the image_id value, however if we want to make the AMI auto update feature a toggle, this would not be possible, as conditionals are not allowed on the lifecycle.
Of course there are some other workarounds, but it feels like this is a design issue that should be solved on the provider level.
What do you think? Thanks a lot for your support!
Community Note
Please vote on this issue by adding a 👍 reaction to help the community and maintainers prioritize this request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
The text was updated successfully, but these errors were encountered:
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
image_id
should not be required when using the AMI auto update feature, as it would conflict with values auto-updated by spot.io.Actual Behavior
image_id
is requiredAdditional Info
Can you elaborate on how AMI auto update should be used with this terraform provider? It seems like the required
image_id
will conflict with changes that are done automatically by the AMI auto update feature.As a temporary workaround we added lifecycle
ignore_changes
to theimage_id
value, however if we want to make the AMI auto update feature a toggle, this would not be possible, as conditionals are not allowed on the lifecycle.Of course there are some other workarounds, but it feels like this is a design issue that should be solved on the provider level.
What do you think? Thanks a lot for your support!
Community Note
The text was updated successfully, but these errors were encountered: