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

Project log exclusion not recreated after being removed #2519

Closed
rolandkool opened this issue Nov 23, 2018 · 1 comment · Fixed by GoogleCloudPlatform/magic-modules#950
Closed
Labels

Comments

@rolandkool
Copy link
Contributor

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 an 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 an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.

Terraform Version

terraform google provider 1.19.1

Affected Resource(s)

  • google_logging_project_exclusion

Terraform Configuration Files

resource "google_logging_project_exclusion" "all-logging-disabled" {
  name = "all-logging-disabled"
  project = "myproject"
  filter = "logName:*"
}

Expected Behavior

When terraform manages a project exclusion and the exclusion is removed outside terraforms control, it fails recreating it. Terraform throws an error in stead when refreshing state:
google_logging_project_exclusion.gcpcompute: google_logging_project_exclusion.all-logging-disabled: Error reading Logging Exclusion all-logging-disabled: Error retrieving logging exclusion for "projects" "myproject": googleapi: Error 404: Exclusion all-logging-disabled does not exist, notFound

Actual Behavior

Expected the logging exclusion to be recreated

Steps to Reproduce

  1. terraform apply on the example tf
  2. In GCP cloud console , go to logging and remove the exclusion. Or turn on log ingestion as the console recognizes the logging to be completely disabled.
  3. rerun terraform.
@ghost
Copy link

ghost commented Dec 27, 2018

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 Dec 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
1 participant