[EVPN] Add Instance Profile Support in Terraform Module #88
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add support for EVPN instance profile configuration on VLANs, enabling both manual EVI and auto EVI with profile modes.
Changes
evpn_instance_protectedmapping for manual EVI configurationevpn_instance_profilemapping for auto EVI with profile supportevpn_instance_profile_protectedmapping for auto EVI protected modeevpn_instanceandevpn_instance_vnimappings (now use new provider YANG path)Dependencies
Depends on Provider PR: CiscoDevNet/terraform-provider-iosxe#349
This PR requires the provider changes to be merged first, as it references new provider attributes.
Testing
YAML Configuration Example
Manual EVI Mode:
Profile Mode (NEW FEATURE):
Breaking Change Migration
The module maintains backward compatibility - users continue using the same YAML field names (
evpn_instance,evpn_instance_vni), which now map to the new provider attributes that use the current YANG path.