Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Sometimes we don't want terraform to redeploy the instance when a new image got added to data.oci_core_images.
So, it will be great if the module support some lifecycle instruction with ignore_changes as we can do to several resources.
Yeah, I know I can hardcode the image ocid in this example, but, hardcoding things is not terraforming, right? Specially if #78 got implemented.
New or Affected Resource(s)
module "instance" {
source = "oracle-terraform-modules/compute-instance/oci"
Potential Terraform Configuration
# Copy-paste any Terraform configurations for how the requested feature may be used.
module "instance" {
source = "oracle-terraform-modules/compute-instance/oci"
version = "2.4.1"
...
lifecycle {
ignore_changes = all
}
}
References
#78
Community Note
Description
Sometimes we don't want terraform to redeploy the instance when a new image got added to
data.oci_core_images.So, it will be great if the module support some
lifecycleinstruction withignore_changesas we can do to several resources.Yeah, I know I can hardcode the image ocid in this example, but, hardcoding things is not terraforming, right? Specially if #78 got implemented.
New or Affected Resource(s)
Potential Terraform Configuration
References
#78