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

add gateway_bypass property #3112

Closed

Conversation

Lucretius
Copy link
Contributor

Resolves #3027 by adding the ability to set express_route_gateway_bypass

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 for the PR @Lucretius,

Is there a reason we are not reading the value back in on read 🤔

Aside from that could we add this property to a test for verification?

@Lucretius
Copy link
Contributor Author

Looks like I was following along with what was done for the other expressroute property - I can add them both to the read func. I will also add it to a test.

@ghost ghost added size/M and removed size/XS labels Mar 27, 2019
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 for adding the test, aside from the test resources being named test_1 this LGTM 👍

Tests are failing with:

resource 'azurerm_express_route_circuit.test' config: unknown resource 'azurerm_resource_group.test' referenced in variable azurerm_resource_group.test.name
        - resource 'azurerm_express_route_circuit.test' config: unknown resource 'azurerm_resource_group.test' referenced in variable azurerm_resource_group.test.location

@katbyte katbyte added this to the v1.24.0 milestone Mar 27, 2019
@Lucretius
Copy link
Contributor Author

Gah, sorry you've had to act as my debugger on this. I do my acceptance testing with a personal subscription of Azure so some of these resources I am hesitant to run when I don't quite understand all of the resource billing :)

@ghost ghost removed the waiting-response label Mar 28, 2019
@tombuildsstuff
Copy link
Contributor

@Lucretius no worries - I've kicked off the tests again so we'll find out shortly 👍

@katbyte
Copy link
Collaborator

katbyte commented Mar 29, 2019

Test ended with the error:


------- Stdout: -------
=== RUN   TestAccAzureRMVirtualNetworkGatewayConnection_expressroute
=== PAUSE TestAccAzureRMVirtualNetworkGatewayConnection_expressroute
=== CONT  TestAccAzureRMVirtualNetworkGatewayConnection_expressroute
--- FAIL: TestAccAzureRMVirtualNetworkGatewayConnection_expressroute (885.46s)
    testing.go:538: Step 0 error: Error applying: 1 error occurred:
        	* azurerm_virtual_network_gateway_connection.test: 1 error occurred:
        	* azurerm_virtual_network_gateway_connection.test: Error waiting for completion of Virtual Network Gateway Connection "acctest-190328215702318119" (Resource Group "acctestRG-190328215702318119"): Code="InvalidOperation" Message="ExpressRouteGatewayByPass is not enabled for this circuit acctest-erc-190328215702318119" Details=[]
        
        
        
        
    testing.go:599: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.

@Lucretius
Copy link
Contributor Author

I’ll go back to the drawing board and try to get a better understanding of this resource before I adjust the test any further. Looks like there is something I am not understanding about how this should be operating. Thanks!

@tombuildsstuff tombuildsstuff added this to the v1.25.0 milestone Mar 29, 2019
@tombuildsstuff
Copy link
Contributor

@Lucretius 👋 would you be able to reach out? [first name]@[company].[com]

@Lucretius
Copy link
Contributor Author

Sure thing @tombuildsstuff - feel free to reach me at [email protected]

@ghost ghost removed the waiting-response label Mar 29, 2019
@tombuildsstuff tombuildsstuff modified the milestones: v1.25.0, v1.26.0 Apr 16, 2019
@katbyte katbyte modified the milestones: v1.26.0, v1.27.0 Apr 17, 2019
@Lucretius
Copy link
Contributor Author

Looks like this logic was included in a recent pull request, closing this PR.

@Lucretius Lucretius closed this Apr 21, 2019
@ghost ghost removed the waiting-response label Apr 21, 2019
@Lucretius Lucretius deleted the express_route_gateway_bypass branch April 21, 2019 06:31
@ghost
Copy link

ghost commented May 17, 2019

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

@ghost
Copy link

ghost commented May 21, 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 May 21, 2019
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.

ExpressRoute Fastpath connection option
3 participants