-
Notifications
You must be signed in to change notification settings - Fork 30
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
terraform-aci-fabric-pod-policy-group "Please add all options to edit" #175
Comments
…roup. Fix for terraform-aci-fabric-pod-policy-group "Please add all options to edit" netascode#175 M: defaults.yaml M: aci_fabric_policies.tf M: terraform-aci-fabric-pod-policy-group
…roup. Fix for terraform-aci-fabric-pod-policy-group "Please add all options to edit" netascode#175 M: defaults.yaml M: aci_fabric_policies.tf M: terraform-aci-fabric-pod-policy-group
…roup. Fix for terraform-aci-fabric-pod-policy-group "Please add all options to edit" netascode#175 M: defaults.yaml M: aci_fabric_policies.tf M: terraform-aci-fabric-pod-policy-group
Custom route reflector, ISIS, and COOP policies cannot be created (there is only the system default), and these do not need to be specified in the pod policy group. Even though technically you could specify "default", it gets applied without doing so. Therefore it only makes sense to add the ability to configure a MACsec policy. This is not yet possible in the module, so perhaps you could consider adding a module for that in conjunction with being able to set it in the pod policy group? |
Can do. I've been updating my macsec policy to include creating fabric macsec policies. I can add this request into that. I also noticed that there's no fabric spine/leaf interface policy group modules, so may create modules for that as well in a separate pr |
For module terraform-aci-fabric-pod-policy-group
I can not add the BGP route reflector policy that I edited in system settings, and I test it out and it does not fill it in as default, also there other policy to edit for example COOP policy etc
The text was updated successfully, but these errors were encountered: