-
Notifications
You must be signed in to change notification settings - Fork 33
Tag Ports Created By CAPO Based on Network or Subnet Attached #166
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
Conversation
…ubnet they are attached to
|
/assign @adduarte |
|
As per offline convo with @adduarte, I added a function to ensure users don't mistakenly duplicate tags for ports, as well as a set of tests to check it. Note that list order is not preserved, but it does not matter in this case. |
|
/retest |
|
/lgtm |
Fedosin
left a comment
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
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Fedosin The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
fix incorrect path description, in future it may corrupt scripting arch. Close openshift#166
Gives users the ability to tag the ports CAPO creates based on the network or subnet they are attached to. Some Usage patterns in the ProviderSpec are as follows:
tag1: all resources created by CAPO
tag2: all ports attached to network net1 created by CAPO
tag3: all ports attached to subnet snet1 created by CAPO
tag4: all ports attached to subnet snet2 created by CAPO
Fixes: OSASINFRA-2348