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

DOCS: Multi-Cloud Transit > enable_firenet vs. enable_transit_firenet #1278

Open
tmcconnaughy opened this issue May 2, 2022 · 0 comments
Open

Comments

@tmcconnaughy
Copy link

Customer is confused at reason why enable_firenet attribute using the resource "aviatrix_transit_gateway" produced the error:

TGW Firenet function is not supported for Azure ARM

Worked with customer to explain that enable_firenet attribute is legacy workflow assuming TGW Firenet and to use enable_transit_firenet instead. The documentation is unclear on which to use or what the workflow expected of enable_firenet vs. enable_transit_firenet will be.

Suggest updating doc to make it clear that when using Aviatrix transit gateway to use enable_transit_firenet and only to use enable_firenet for legacy TGW workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant