-
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
Add support for Shielded VMs #3209
Comments
hi! I'd like to work on this if no one else is. |
Go ahead! I've marked the issue assigned to HashiBot to indicate that you're working on it. (We can only assign users with merge access to issues / PRs, so we mark community members with HashiBot) |
hi @rileykarson after i submitted this PR i saw the stuff about magic modules and that most of the activity for these resources is coming from there. just wanted to confirm whether that's how these changes ought to be made instead? |
Either is fine! The code in this repository is managed by Magic Modules so that this and the beta repo stay in sync. To keep the contribution process similar to other providers, Google provider maintainers upstream PRs submitted against this repo / the beta repo to MM. |
Closed with #3531 |
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! |
Community Note
Description
Shielded VMs give users the ability to create instances with verifiable integrity to prevent against malware and rootkits.
Sample from compute engine REST API:
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: