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

The uppercase VulnerabilityAssessmentName returned by the DatabaseVulnerabilityAssessments_CreateOrUpdate API #17192

Open
sinbai opened this issue Dec 30, 2021 · 4 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. SQL

Comments

@sinbai
Copy link

sinbai commented Dec 30, 2021

When creating a DatabaseVulnerabilityAssessments resource. The value of VulnerabilityAssessmentName is fixed as "default" , but the name in response body is "Default". details:

The response body is:

{
  "properties": {
    "storageContainerPath": "https://accsa.blob.core.windows.net/testsc/",
    "recurringScans": {
      "isEnabled": false,
      "emailSubscriptionAdmins": true,
      "emails": []
    }
  },
  "id": "/subscriptions/xxx/resourceGroups/testRG-mssql/providers/Microsoft.Sql/servers/testsqlserver/databases/testdb/vulnerabilityAssessments/Default",
  "name": "Default",
  "type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments"
}

Actual: The "name" in response body is "Default". The VulnerabilityAssessmentName of "id" in response body is "Default".
Expected: All VulnerabilityAssessmentName in response body should be "default".

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Dec 30, 2021
@sinbai sinbai changed the title The uppercase VulnerabilityAssessmentName returned by the DatabaseVulnerabilityAssessments_CreateOrUpdate API. The uppercase VulnerabilityAssessmentName returned by the DatabaseVulnerabilityAssessments_CreateOrUpdate API Dec 30, 2021
@ruowan ruowan added the SQL label Dec 31, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 31, 2021
@ruowan ruowan added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. Service Attention Workflow: This issue is responsible by Azure service team. labels Dec 31, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 31, 2021
@ghost
Copy link

ghost commented Dec 31, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub.

Issue Details

When creating a DatabaseVulnerabilityAssessments resource. The value of VulnerabilityAssessmentName is fixed as "default" , but the name in response body is "Default". details:

The response body is:

{
  "properties": {
    "storageContainerPath": "https://accsa.blob.core.windows.net/testsc/",
    "recurringScans": {
      "isEnabled": false,
      "emailSubscriptionAdmins": true,
      "emails": []
    }
  },
  "id": "/subscriptions/xxx/resourceGroups/testRG-mssql/providers/Microsoft.Sql/servers/testsqlserver/databases/testdb/vulnerabilityAssessments/Default",
  "name": "Default",
  "type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments"
}

Actual: The "name" in response body is "Default". The VulnerabilityAssessmentName of "id" in response body is "Default".
Expected: All VulnerabilityAssessmentName in response body should be "default".

Author: sinbai
Assignees: -
Labels:

question, SQL, Service Attention, customer-reported, needs-triage

Milestone: -

@MrImpossibru
Copy link

@ruowan will this be fixed soon? It broke managing Azure SQL VAs via Terraform. Thanks.

@catt231
Copy link

catt231 commented Feb 4, 2022

agreed this is forcing replacements of resources and creating noise in my pipelines I don't need... would love to see it resolved soon please

@krohm
Copy link

krohm commented Dec 1, 2022

Any progress on that ?
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. SQL
Projects
None yet
Development

No branches or pull requests

5 participants