Adding support for Static AAEP configuration directly from EPG #341
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
This pull request introduces introduces support for the Static AAEP configuration directly from the EPG:
-Pre-Existing Files:
aci_tenants.tf
defaults/defaults.yaml
modules/terraform-aci-endpoint-group/README.md
modules/terraform-aci-endpoint-group/main.tf
modules/terraform-aci-endpoint-group/variables.tf
-Motivation
ACI release 6.1(3) introduces support to configuring AAEP association directly from the EPG. This PR contains the code to support this.
Related Issues
Issue https://wwwin-github.cisco.com/netascode/nac-aci/issues/648 in the ACI as Code Planning backlog
This PR is also related to #279 . This is the original PR.
The original PR was using aaep as attribute and might cause confusion, this was change to "name" to aso keep consistency with internal code.