-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Docs make importing google_monitoring_alert_policy
… hard
#19453
Open
roy-work opened this issue
Sep 12, 2024
· 2 comments
· May be fixed by GoogleCloudPlatform/magic-modules#11831
Open
Docs make importing google_monitoring_alert_policy
… hard
#19453
roy-work opened this issue
Sep 12, 2024
· 2 comments
· May be fixed by GoogleCloudPlatform/magic-modules#11831
Comments
github-actions
bot
added
forward/review
In review; remove label to forward
service/monitoring-alerting
labels
Sep 12, 2024
Confirmed issue! After following the steps and checking out in the documentation and in the @hao-nan-li shared link results very complicated to import this resource and the terraform registry documentation doesn't help so much. |
ggtisc
added
documentation
and removed
bug
forward/review
In review; remove label to forward
labels
Sep 18, 2024
z-nand
added a commit
to z-nand/magic-modules
that referenced
this issue
Sep 26, 2024
Adds support for severity options in AlertPolicy. I acknowledge that I have: Searched through the issue tracker for an open issue that this either resolves or contributes to, commented on it to claim it, and written "fixes {url}" or "part of {url}" in this PR description. If there were no relevant open issues, I opened one and commented that I would like to work on it (not necessary for very small changes). Ensured that all new fields I added that can be set by a user appear in at least one example (for generated resources) or third_party test (for handwritten resources or update tests). Generated Terraform providers, and ran make test and make lint in the generated providers to ensure it passes unit and linter tests. Ran relevant acceptance tests using my own Google Cloud project and credentials (If the acceptance tests do not yet pass or you are unable to run them, please let your reviewer know). Read the Release Notes Guide before writing my release note below.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Community Note
Terraform Version & Provider Version(s)
Terraform v1.5.7
on darwin_amd64
Affected Resource(s)
google_monitoring_alert_policy
Terraform Configuration
Debug Output
No response
Expected Behavior
To be able to import these
Actual Behavior
The docs say to just use
{{ name }}
, which since these are project-scoped, basically cannot be correct; there must be a project ID in there, somewhere.In
gcloud
, there is however aname
field:If I attempt to use that, however,
The code seems to want a space-separated project ID; if we try that:
I was about to submit this bug report and tried one last permutation:
That worked. I think the documentation could probably be better here… and help me understand what
name
is referring to? (As it doesn't match the name a user supplies in the UI.)(So, if you're reading this and wondering how to get that string, run,
and it's the
name
field.)Steps to reproduce
terraform import google_monitoring_alert_policy.…
Important Factoids
No response
References
No response
b/368130892
The text was updated successfully, but these errors were encountered: