You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
We could collectively benefit from forming a Working Group related to Cisco ACI and MultiSite integration. We have quite some contributors and users that are interested in improving this integration.
So this issue is a call to potential interested parties (earlier and existing contributors to Ansible). The benefits of having a Working Group is that members of the Working Group can:
test, review and add shipits to existing ACI and MultiSite PRs
work collectively on a ACI and MultiSite roadmap
provide a single-point-of-contact for interested ACI and MultiSite contributors
have a $team_aci in BOTMETA.yml for auto-notifying team members
implement auto-labeling ACI issues and PRs
Since we don't have any ACI infrastructure for automated testing in Shippable CI, collaborating on modules like this is important for the quality of the modules. We do have a public/shared infrastructure at DevNet for ad-hoc testing.
The text was updated successfully, but these errors were encountered:
Any plans to modernize aci_epg to include support for declaring EPG contract masters? This functionality has been around for some time in ACI and I am somewhat surprised its not included in the module.
We could collectively benefit from forming a Working Group related to Cisco ACI and MultiSite integration. We have quite some contributors and users that are interested in improving this integration.
So this issue is a call to potential interested parties (earlier and existing contributors to Ansible). The benefits of having a Working Group is that members of the Working Group can:
Since we don't have any ACI infrastructure for automated testing in Shippable CI, collaborating on modules like this is important for the quality of the modules. We do have a public/shared infrastructure at DevNet for ad-hoc testing.
The text was updated successfully, but these errors were encountered: