Skip to content

Extend VRF resource to use custom templates#120

Open
jgomezve wants to merge 4 commits intoCiscoDevNet:masterfrom
jgomezve:jg-vrf-resource-custom-template
Open

Extend VRF resource to use custom templates#120
jgomezve wants to merge 4 commits intoCiscoDevNet:masterfrom
jgomezve:jg-vrf-resource-custom-template

Conversation

@jgomezve
Copy link
Copy Markdown

@jgomezve jgomezve commented Feb 1, 2023

Fix #111

"asn" : "4201020601"
"vrfIntfDescription" : ""
"vrfSegmentId" : "50050"
"vrfName" : "check3"
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Even if the VRF Name and the VRF Segment ID are inputs of the resource, the values must be set inside the template properties as well. Otherwise Terraform will try to update does values in a subsequent terraform apply. This is because the Read Operataion identifies those keys but the Schema does not have them

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

The same applies for the Network Resource in the PR #121

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Got it. This PR is working for me. Tested it out with different scenarios.

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

Successfully merging this pull request may close these issues.

Support VRF and Networks using custom templates

2 participants