-
Notifications
You must be signed in to change notification settings - Fork 101
Addition of service graph modules and their test files (DCNE-410) #754
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: master
Are you sure you want to change the base?
Conversation
…h_template_node module
…tion_interface_context module
plugins/modules/aci_l4l7_service_graph_template_abs_connection.py
Outdated
Show resolved
Hide resolved
…ervice_graph_template modules
- cisco.aci.annotation | ||
|
||
notes: | ||
- The I(tenant), I(graph), I(contract) and I(node) must exist before using this module in your playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The I(tenant), I(graph), I(contract) and I(node) must exist before using this module in your playbook. | |
- The O(tenant), O(graph), O(contract) and O(node) must exist before using this module in your playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment was already made by @gmicol in a related PR. In ansible ACI collection we've been using I() for Input in the other modules. I believe that this usage should be consistent within this collection.
type: str | ||
permit_handoff: | ||
description: | ||
- Indicates whether to allow handoff of traffic to the associated logical interface. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does APIC default these Booleans to anything when unset? permit_handoff
, acl
, rule_type
?
# child_configs.append( | ||
# { | ||
# "vnsRsLIfCtxToBD": { | ||
# "attributes": { | ||
# "dn": child.get("vnsRsLIfCtxToBD").get("attributes").get("dn"), | ||
# "status": "deleted", | ||
# } | ||
# } | ||
# } | ||
# ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# child_configs.append( | |
# { | |
# "vnsRsLIfCtxToBD": { | |
# "attributes": { | |
# "dn": child.get("vnsRsLIfCtxToBD").get("attributes").get("dn"), | |
# "status": "deleted", | |
# } | |
# } | |
# } | |
# ) |
Not sure if you need the previous code. I think the comment is fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We left the code commented in other modules as well. I left it to be consistent with them..
- cisco.aci.aci | ||
- cisco.aci.annotation | ||
notes: | ||
- The I(tenant), I(contract), I(graph), I(device) and I(node) must exist before using this module in your playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The I(tenant), I(contract), I(graph), I(device) and I(node) must exist before using this module in your playbook. | |
- The O(tenant), O(contract), O(graph), O(device) and O(node) must exist before using this module in your playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as above
- cisco.aci.annotation | ||
- cisco.aci.owner | ||
notes: | ||
- The I(tenant) must exist before using this module in your playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The I(tenant) must exist before using this module in your playbook. | |
- The O(tenant) must exist before using this module in your playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as above
choices: [ redirect, unspecified ] | ||
is_copy: | ||
description: | ||
- Whether the device is a copy device. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
default?
type: bool | ||
share_encap: | ||
description: | ||
- Whether to share encapsulation across the service graph. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
default?
- cisco.aci.annotation | ||
- cisco.aci.owner | ||
notes: | ||
- The I(tenant), I(service_graph) and I(device) must exist before using this module in your playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The I(tenant), I(service_graph) and I(device) must exist before using this module in your playbook. | |
- The O(tenant), O(service_graph) and O(device) must exist before using this module in your playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as above
- cisco.aci.annotation | ||
- cisco.aci.owner | ||
notes: | ||
- The I(tenant) and I(service_graph) must exist before using this module in your playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The I(tenant) and I(service_graph) must exist before using this module in your playbook. | |
- The O(tenant) and O(service_graph) must exist before using this module in your playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.