-
Notifications
You must be signed in to change notification settings - Fork 98
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
ACI Contract Subject Labels #310
Comments
Hi @markciecior, Thank you for your issue raise and contribution. I would like to ask you a few things in regards to your contribution, could you please follow the following documentation/process: https://github.com/shrsr/ansible/blob/devel/docs/docsite/rst/dev_guide/developing_modules_general_aci.rst. This includes creating tests for the developed module. Besides this I was wondering your exact use-case and if you were aware of the https://github.com/CiscoDevNet/ansible-aci/blob/master/plugins/modules/aci_epg_to_contract.py module. Code wise this could provide some insights for simplification of your code. Also this raises a question to me if we need a separate module for this functionality or if this can be included into existing module, what are your thoughts on this? |
Hi @akinross, I'm aware my contribution doesn't include any tests today. If the use case is deemed legitimate I will add those. When a subject and/or provider labels are used with contracts, those labels need to be added to the EPG (which is possible using the module above), and to the contract subject. I didn't see any mechanism to add the labels to the contract subject, which is what sent me down this path. As for folding this into another module, I see the child_classes construct now. That would make more sense than a separate module. I will pursue that path instead. Thanks. |
I created a new PR using the technique mentioned above in #319. |
Community Note
Description
!new_module
New or Affected Module(s):
APIC version and APIC Platform
Collection versions
References
The text was updated successfully, but these errors were encountered: