John Yanez
@johnyanez.bsky.social
Personal: Husband, Father, Husky Whisper, Gamer and Truck Enthusiasts
Work: Cloud Network Engineer, DevOps, Driven to innovate and build amazing
GitHub: https://github.com/networkdude17
Work: Cloud Network Engineer, DevOps, Driven to innovate and build amazing
GitHub: https://github.com/networkdude17
Yeah, there are many changes in the core and management resources.
Plan: 14 to add, 42 to change, 10 to destroy.
Lots of which are version changes in polices, so I'm sure something will break there lol.
Plan: 14 to add, 42 to change, 10 to destroy.
Lots of which are version changes in polices, so I'm sure something will break there lol.
April 28, 2025 at 2:48 PM
Yeah, there are many changes in the core and management resources.
Plan: 14 to add, 42 to change, 10 to destroy.
Lots of which are version changes in polices, so I'm sure something will break there lol.
Plan: 14 to add, 42 to change, 10 to destroy.
Lots of which are version changes in polices, so I'm sure something will break there lol.
After that, when I run a plan, the only changes are Palo Alto Firewall-related and no other changes. So, allowing version 4 of azurerm does not seem to introduce changes, at least for the networking side.
April 28, 2025 at 2:30 PM
After that, when I run a plan, the only changes are Palo Alto Firewall-related and no other changes. So, allowing version 4 of azurerm does not seem to introduce changes, at least for the networking side.
But if I fork your module and update the following:
April 28, 2025 at 2:22 PM
But if I fork your module and update the following: