-
Notifications
You must be signed in to change notification settings - Fork 59
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
OSD-19729: Enables ocm backplane login to provide default namespace as an argument #374
Conversation
@amej: This pull request references OSD-19729 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 story to target the "4.16.0" version, but no target version was set. In response to this:
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. |
Skipping CI for Draft Pull Request. |
@amej: This pull request references OSD-19729 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 story to target the "4.16.0" version, but no target version was set. In response to this:
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. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #374 +/- ##
==========================================
+ Coverage 44.50% 44.61% +0.11%
==========================================
Files 62 62
Lines 5159 5173 +14
==========================================
+ Hits 2296 2308 +12
- Misses 2547 2548 +1
- Partials 316 317 +1
|
@amej: This pull request references OSD-19729 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 story to target the "4.16.0" version, but no target version was set. In response to this:
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. |
@amej: This pull request references OSD-19729 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 story to target the "4.16.0" version, but no target version was set. In response to this:
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. |
@Tafhim , @supreeth7 and @devppratik : Please can you review ? |
@amej Can you pls squash the commits ? |
/label tide/merge-method-squash |
@devppratik : Does this label free me up from the work of squashing commits locally on my laptop & force pushing them to the fork's feature branch? |
@amej: This pull request references OSD-19729 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 story to target the "4.16.0" version, but no target version was set. In response to this:
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. |
@amej: This pull request references OSD-19729 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 story to target the "4.16.0" version, but no target version was set. In response to this:
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. |
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.
I have reviewed the comments. 0560e97 contains the recommendations.
@amej let me know if you need any help to squash the commit manually |
@supreeth7 : |
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.
@supreeth7 : Changes reviewed and action taken including squashing commits locally & pushing them.
@amej thanks for addressing the review comments. The commit number is too wide for it to be merged, even with the tide plugin squashing it, can you try squashing your commits without any trailing commit history? |
…f login Signed-off-by: Ameya Sathe <asathe@redhat.com>
@supreeth7 : Please find a single commit now. I force pushed the changes to the OSD-19729 branch. |
@devppratik guided me to opt for the easy solution . |
@amej: 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. |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amej, supreeth7 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 |
What type of PR is this?
What this PR does / Why we need it?
As a SRE, I want backplane login to prompt for a default namespace for me to run commands like oc debug node/xxx.
Which Jira/Github issue(s) does this PR fix?
Resolves #OSD-19729
Special notes for your reviewer
Once merged,
./ocm-backplane login --help
will display./ocm-backplane login asathe-19729
oc project
./ocm-backplane login --namespace openshift-sre-pruning 28lje9u3jd59j3dmf36sojgpa32qrag3
oc project
./ocm-backplane login --namespace "" asathe-19729
./ocm-backplane login --namespace 'kube_system' asathe-19729
Hence, the command "oc status" will display the following error
error: Missing or incomplete configuration info. Please point to an existing, complete config file:
Please do refer to the prior discussion in the #315 .
Pre-checks (if applicable)