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

azurerm_mysql_virtual_network_rule - remove subnet cfg check as its no longer required #5568

Merged
merged 2 commits into from
Jan 31, 2020

Conversation

titilambert
Copy link
Contributor

@titilambert titilambert commented Jan 30, 2020

Fixs #4392

@ghost ghost added the size/S label Jan 30, 2020
@katbyte katbyte changed the title Fix #4392 azurerm_mysql_virtual_network_rule - remove subnet cfg check as its no longer required Jan 31, 2020
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @titilambert,

Could we get a test with an improperly configured subnet to verify that the api has actually been fixed? thanks!

@titilambert
Copy link
Contributor Author

Hi @titilambert,

Could we get a test with an improperly configured subnet to verify that the api has actually been fixed? thanks!

Thanks for your answer !
Do you have an example to see how to do it correctly ? (I don't find one)

Thanks

@ghost ghost removed the waiting-response label Jan 31, 2020
@katbyte
Copy link
Collaborator

katbyte commented Jan 31, 2020

@titilambert,

You can take an existing test and create a new one where in the:

resource "azurerm_subnet" "test" {
  name                 = "acctestsubnet%d"
  resource_group_name  = "${azurerm_resource_group.test.name}"
  virtual_network_name = "${azurerm_virtual_network.test.name}"
  address_prefix       = "10.7.29.0/29"
  service_endpoints    = ["Microsoft.Sql"]
}

section remove the service_endpoints = ["Microsoft.Sql"] line and see what happens.

@titilambert
Copy link
Contributor Author

@katbyte Thanks

....... make acctests SERVICE='mysql' TESTARGS='-run=TestAccAzureRMMySqlVirtualNetworkRule_badsubnet'
==> Checking that code complies with gofmt requirements...
==> Checking that Custom Timeouts are used...
TF_ACC=1 go test -v ./azurerm/internal/services/mysql/tests/ -run=TestAccAzureRMMySqlVirtualNetworkRule_badsubnet -timeout 180m -ldflags="-X=github.com/terraform-providers/terraform-provider-azurerm/version.ProviderVersion=acc"
=== RUN   TestAccAzureRMMySqlVirtualNetworkRule_badsubnet
=== PAUSE TestAccAzureRMMySqlVirtualNetworkRule_badsubnet
=== CONT  TestAccAzureRMMySqlVirtualNetworkRule_badsubnet

--- PASS: TestAccAzureRMMySqlVirtualNetworkRule_badsubnet (381.34s)
PASS
ok  	github.com/terraform-providers/terraform-provider-azurerm/azurerm/internal/services/mysql/tests	381.353s

@ghost ghost removed the waiting-response label Jan 31, 2020
@ghost ghost added size/M and removed size/S labels Jan 31, 2020
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @titilambert! LGTM now

@katbyte katbyte merged commit 0814e48 into hashicorp:master Jan 31, 2020
@katbyte katbyte added this to the v1.43.0 milestone Jan 31, 2020
katbyte added a commit that referenced this pull request Jan 31, 2020
@ghost
Copy link

ghost commented Feb 4, 2020

This has been released in version 1.43.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.43.0"
}
# ... other configuration ...

@ghost
Copy link

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

Successfully merging this pull request may close these issues.

2 participants