关于“管理 Terraform 状态”的评价

Nomula S. · 已于 3 months前审核

Oleksandr V. · 已于 3 months前审核

Gonga A. · 已于 3 months前审核

Shivani-Rajesh D. · 已于 3 months前审核

Anupriya P. · 已于 3 months前审核

Bibhishan D. · 已于 3 months前审核

Tamil S. · 已于 3 months前审核

Saranya S. · 已于 3 months前审核

Felix K. · 已于 3 months前审核

sridhar n. · 已于 3 months前审核

Sagar A. · 已于 3 months前审核

Krishna P. · 已于 3 months前审核

Priyanshu K. · 已于 3 months前审核

Aromal M. · 已于 3 months前审核

Vignesh K. · 已于 3 months前审核

Mayur urs N. · 已于 3 months前审核

VADDE VENKATESH U. · 已于 3 months前审核

Viresh S. · 已于 3 months前审核

Yuvaraj R. · 已于 3 months前审核

After the step "Copy your Terraform state into your docker.tf file", terraform plan failed: 1. This fails because there is still a docker_container.web resource in main.tf. I had to remove that first before seeing the errors about read-only arguments. 2. As of writing (using docker provider version 3.9.0), the "links" argument is no longer present in `terraform show` output, so there was no warning about a deprecated argument. 3. The terraform show output uses "nginx:latest" in "image" instead of the sha256. After removing unneeded attributes in docker.tf, terraform plan now says that the container will be replaced: ``` Terraform will perform the following actions: # docker_container.web must be replaced -/+ resource "docker_container" "web" { ... + env = (known after apply) # forces replacement ``` The subsequent step (changing image = docker_image.nginx.image_id) then requires replacing the container again because the image attribute in the state was "nginx:latest", not "sha256:..."

Gerardus Samudra S. · 已于 3 months前审核

Luis Miguel R. · 已于 3 months前审核

Francisco C. · 已于 3 months前审核

Marcus B. · 已于 3 months前审核

James P. · 已于 3 months前审核

Navya sree N. · 已于 3 months前审核