Skip to content
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

CNV-36170: Multi create form #16

Merged
merged 1 commit into from
Mar 28, 2024

Conversation

upalatucci
Copy link

@upalatucci upalatucci commented Mar 20, 2024

The annotation syntax is explainer right here: https://docs.openshift.com/container-platform/4.15/networking/multiple_networks/configuring-multi-network-policy.html#nw-multi-network-policy-differences_configuring-multi-network-policy

Most of the cases would be just one nad. But in case the user wants multiple nads, the names should have , between them.
In case the nad is from another namespace we have to write <namespace>/<name> but backend suggested to put everytime the namespace so no one will be confused

@openshift-ci openshift-ci bot requested review from metalice and tnisan March 20, 2024 14:52
Copy link

openshift-ci bot commented Mar 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: upalatucci

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 20, 2024
@upalatucci upalatucci force-pushed the multi-create-form branch 4 times, most recently from b46e0bf to 4ce54dd Compare March 21, 2024 10:21
@upalatucci upalatucci force-pushed the multi-create-form branch 2 times, most recently from 4a11aa0 to c89af52 Compare March 25, 2024 17:26
@upalatucci upalatucci changed the title Multi create form CNV-36170: Multi create form Mar 26, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 26, 2024

@upalatucci: This pull request references CNV-36170 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.16.0" version, but no target version was set.

In response to this:

The annotation syntax is explainer right here: https://docs.openshift.com/container-platform/4.15/networking/multiple_networks/configuring-multi-network-policy.html#nw-multi-network-policy-differences_configuring-multi-network-policy

Most of the cases would be just one nad. But in case the user wants multiple nads, the names should have , between them.
In case the nad is from another namespace we have to write <namespace>/<name> but backend suggested to put everytime the namespace so no one will be confused

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 26, 2024
@upalatucci
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 26, 2024

@upalatucci: This pull request references CNV-36170 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.16.0" version, but no target version was set.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@upalatucci upalatucci force-pushed the multi-create-form branch 2 times, most recently from 7f3a11e to 70d0f06 Compare March 27, 2024 11:47
Copy link

openshift-ci bot commented Mar 28, 2024

@upalatucci: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@metalice
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 28, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 7888156 into openshift:main Mar 28, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants