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

New-Feature-Request Storage Threat Detection Policy #3670

Closed
techjacker opened this issue Jun 14, 2019 · 3 comments · Fixed by #3782
Closed

New-Feature-Request Storage Threat Detection Policy #3670

techjacker opened this issue Jun 14, 2019 · 3 comments · Fixed by #3782

Comments

@techjacker
Copy link

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

Description

Enable threat detection on storage accounts.

New or Affected Resource(s)

  • azurerm_storage_account

Potential Terraform Configuration

Copy the way it has been implemented for azurerm_sql_database

threat_detection_policy = {}

References

Go SDK does not appear to support it.

Azure API does have it:
https://docs.microsoft.com/en-us/rest/api/securitycenter/advancedthreatprotection/create

@ghost
Copy link

ghost commented Jul 30, 2019

This has been released in version 1.32.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 1.32.0"
}
# ... other configuration ...

@techjacker
Copy link
Author

Thank you very much!

@ghost
Copy link

ghost commented Aug 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 Aug 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants