-
Notifications
You must be signed in to change notification settings - Fork 44
Added support for Static AAEPs via EPG - fvRsAepAtt #279
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
base: main
Are you sure you want to change the base?
Conversation
|
In this state, subsequent deployments of fvRsAepAtt objects will consistently come back with changed annotations due to annotation being utilized to indicate if the relationship to AAEP has been formed properly. I have not seen an annotation used to indicate the formation of a relationship before. Is this intended or a misuse of annotation? For now I have set annotation to be ignored. |
|
@manofcolombia Let me try to figure out the issue with the Annotation but this is also the case in ACI 614h so for now I think we can just ignore it as you did in the code and potentially improve this once ACI address this. |
|
@manofcolombia I have confirmed with engineering this was an oversight and will be fixed in an upcoming release but for now we need to go on with your workaround. I will open a cisco defect and link it here tomorrow :) |
Thanks for looking into this. I will be interested in the bug id, once it's public. I've got a few things manually deployed this way already so I just want to be aware when they change the object props to test it in my lab before the prod upgrade. |
|
@manofcolombia I have created the bug: CSCws18431 ACI fvRsAepAtt annotation should not be set by APIC Might take a moment before is available publicly |
Tested on apic: 6.1.3g
Here is a sample of the yaml for updating the nac json schema