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

Atp settings are not supported on resources of type servers (PostgreSQL) #6610

Closed
oscarmon7 opened this issue Apr 24, 2020 · 3 comments
Closed

Comments

@oscarmon7
Copy link

Hello,
using provider.azurem v2.2.0 I'm getting the below error when trying to activate ATP in a PostgreSQL server.

Error: Error checking for presence of existing Advanced Threat Protection for resource "/subscriptions/***/resourceGroups/***/providers/Microsoft.DBforPostgreSQL/servers/mypgserver": security.AdvancedThreatProtectionClient#Get: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="Not Supported" Message="Atp settings are not supported on resources of type servers"

on resources\postgres.tf line 148, in resource "azurerm_advanced_threat_protection" "atp":
148: resource "azurerm_advanced_threat_protection" "atp" {

There is an issue reporting this same topic #5238 which was closed without a proper resolution. I would appreciate your feedback.

Thanks.

@oscarmon7 oscarmon7 changed the title Atp settings are not supported on resources of type servers Atp settings are not supported on resources of type servers (PostgreSQL) Apr 24, 2020
@pearcec
Copy link
Contributor

pearcec commented Apr 25, 2020

Seems similar to this issue #5629.

@katbyte
Copy link
Collaborator

katbyte commented Apr 26, 2020

@oscarmon7 - this is a duplicate of #5629so as such i am going to close to keep discussion on one issue. thanks thou!

@ghost
Copy link

ghost commented May 26, 2020

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 May 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants