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

Add support for scheduled snapshots for persistent disk #3062

Closed
Chupaka opened this issue Feb 15, 2019 · 5 comments · Fixed by GoogleCloudPlatform/magic-modules#1850
Closed

Comments

@Chupaka
Copy link
Contributor

Chupaka commented Feb 15, 2019

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

Scheduled snapshots feature is promoted to beta now, so it worth adding to google-beta provider :)
https://cloud.google.com/compute/docs/disks/scheduled-snapshots

@ghost ghost added the enhancement label Feb 15, 2019
@emilymye
Copy link
Contributor

For reference, this would entail adding resource policies as a resource: https://cloud.google.com/compute/docs/reference/rest/beta/resourcePolicies/

@Lirt
Copy link

Lirt commented Jul 1, 2019

Hey,

I've encountered some permission problems with the scheduled snapshot resource policy. I am not sure if this is a bug in provider, but maybe somebody else bumped into this?

  1. Created resource policy:
resource "google_compute_resource_policy" "XYZ-snapshot-schedule" {
  name        = "XYZ-snapshot-schedule"
  provider    = "google-beta"
  project     = "project1"
  region      = "us-central1"

  snapshot_schedule_policy {
    schedule {
      daily_schedule {
        days_in_cycle = 1
        start_time    = "02:00"
      }
    }
    retention_policy {
      max_retention_days    = 7
      on_source_disk_delete = "APPLY_RETENTION_POLICY"
    }
    snapshot_properties {
      labels = {
        app      = "XYZ"
      }
    }
  }
}
  1. Attached it manually to disk.
  2. terraform apply worked fine, but now when I hit terraform plan again I have this error:
Error: Error reading ComputeResourcePolicy "XYZ-snapshot-schedule": googleapi: 
Error 403: Required 'compute.resourcePolicies.get' permission for 
'projects/<PROJECT_NAME>/regions/us-central1/resourcePolicies/<XYZ>-snapshot-schedule',
forbidden.
  1. Terraform user has these rights - Compute Viewer, Project Viewer, Role Viewer, Service Account User, Storage Admin

Compute Viewer should be enough for permission compute.resourcePolicies.get according to https://cloud.google.com/iam/docs/understanding-roles.

@tysen
Copy link

tysen commented Jul 1, 2019

Hi @Lirt, I attempted to repro this using admin credentials and terraform plan did not fail in the way you observed. Is it possible for you to try with more permissions?

@Lirt
Copy link

Lirt commented Jul 2, 2019

I solved it, issue was I didn't have specified google-beta provider explicitly. Anyway, thank you for reproducing @tysen.

@ghost
Copy link

ghost commented Jul 6, 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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Jul 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants