Skip to content
New issue

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 Run: await service ready status before finishing refresh #4335

Closed
rileykarson opened this issue Aug 26, 2019 · 3 comments
Closed

Cloud Run: await service ready status before finishing refresh #4335

rileykarson opened this issue Aug 26, 2019 · 3 comments
Labels
enhancement mmv1-generator Provider-wide changes to resource templates or other generator changes

Comments

@rileykarson
Copy link
Collaborator

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. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Today, this fails with the following error:

Error: Invalid index

  on main.tf line 21, in locals:
  21:     for cond in google_cloud_run_service.default.status[0].conditions :
    |----------------
    | google_cloud_run_service.default.status is empty list of object

The given key does not identify an element in this collection value.

Ideally, we'd wait on the status being ready (or another terminal state) in the Read function of the resource. That would allow interpolation off of the status fields to work.

New or Affected Resource(s)

  • google_cloud_run_service

Potential Terraform Configuration

resource "google_cloud_run_service" "default" {
  name     = "my-service"
  location = "us-central1"
  provider = "google-beta"

  metadata {
    namespace = "my-project"
  }

  spec {
    containers {
      image = "gcr.io/cloudrun/hello"
    }
  }
}

# The Service is ready to be used when the "Ready" condition is True
# Due to Terraform and API limitations this is best accessed through a local variable
locals {
  cloud_run_status = {
    for cond in google_cloud_run_service.default.status[0].conditions :
    cond.type => cond.status
  }
}

output "isReady" {
  value = local.cloud_run_status["Ready"] == "True"

References

  • #0000
@chrisst
Copy link
Contributor

chrisst commented Sep 2, 2019

Should be fixed by #4091

@rileykarson
Copy link
Collaborator Author

Ah cool, managed to miss that. closing as dupe.

@ghost
Copy link

ghost commented Oct 4, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Oct 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement mmv1-generator Provider-wide changes to resource templates or other generator changes
Projects
None yet
Development

No branches or pull requests

2 participants