Skip to content

SREP-974: managed-script describe-nodes should accept parameters by environment variables#219

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:mainfrom
MateSaary:srep-974-describe-node-flag
Aug 19, 2025
Merged

SREP-974: managed-script describe-nodes should accept parameters by environment variables#219
openshift-merge-bot[bot] merged 2 commits intoopenshift:mainfrom
MateSaary:srep-974-describe-node-flag

Conversation

@MateSaary
Copy link
Member

@MateSaary MateSaary commented Jul 16, 2025

What type of PR is this?

feature

What this PR does / Why we need it?

This PR improves upon the describe-nodes command by accepting individual env variables as parameters, and as a direct follow-up for openshift/backplane-cli#731, invalid parameters or lack of essential parameters will now throw an error immediately instead of creating the job (and requiring the user to view logs to obtain source of the error).

Which Jira/Github issue(s) does this PR fix?

Resolves # SREP-974

Special notes for your reviewer

Relies on openshift/backplane-cli#731, do not merge until promotion.

Pre-checks (if applicable)

  • Validated the changes in a cluster
  • Included documentation changes with PR

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 16, 2025

@MateSaary: This pull request references SREP-974 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 task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

What type of PR is this?

feature

What this PR does / Why we need it?

This PR improves upon the describe-nodes command by accepting individual env variables as parameters, and as a direct follow-up for openshift/backplane-cli#731, invalid parameters or lack of essential parameters will now throw an error immediately instead of creating the job (and requiring the user to view logs to obtain source of the error).

Which Jira/Github issue(s) does this PR fix?

Resolves # SREP-974

Special notes for your reviewer

Follow-up for openshift/backplane-cli#731, do not merge until promotion.

Pre-checks (if applicable)

  • Validated the changes in a cluster
  • Included documentation changes with PR

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 Jul 16, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 16, 2025
@MateSaary
Copy link
Member Author

/hold

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 16, 2025

@MateSaary: This pull request references SREP-974 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 task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

What type of PR is this?

feature

What this PR does / Why we need it?

This PR improves upon the describe-nodes command by accepting individual env variables as parameters, and as a direct follow-up for openshift/backplane-cli#731, invalid parameters or lack of essential parameters will now throw an error immediately instead of creating the job (and requiring the user to view logs to obtain source of the error).

Which Jira/Github issue(s) does this PR fix?

Resolves # SREP-974

Special notes for your reviewer

Follow-up for openshift/backplane-cli#731, do not merge until promotion.

Pre-checks (if applicable)

  • Validated the changes in a cluster
  • Included documentation changes with PR

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 openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 16, 2025
@MateSaary MateSaary changed the title [WIP] SREP-974: managed-script describe-nodes should accept parameters by environment variables SREP-974: managed-script describe-nodes should accept parameters by environment variables Jul 16, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 16, 2025
@openshift-ci openshift-ci bot requested review from Dee-6777 and MitaliBhalla July 16, 2025 14:33
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 16, 2025

@MateSaary: This pull request references SREP-974 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 task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

What type of PR is this?

feature

What this PR does / Why we need it?

This PR improves upon the describe-nodes command by accepting individual env variables as parameters, and as a direct follow-up for openshift/backplane-cli#731, invalid parameters or lack of essential parameters will now throw an error immediately instead of creating the job (and requiring the user to view logs to obtain source of the error).

Which Jira/Github issue(s) does this PR fix?

Resolves # SREP-974

Special notes for your reviewer

Relies on openshift/backplane-cli#731, do not merge until promotion.

Pre-checks (if applicable)

  • Validated the changes in a cluster
  • Included documentation changes with PR

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.

@MateSaary
Copy link
Member Author

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MateSaary

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

The pull request process is described here

Details 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 Jul 21, 2025
@MateSaary MateSaary requested a review from Dee-6777 July 23, 2025 07:56
@MateSaary MateSaary force-pushed the srep-974-describe-node-flag branch from 8112b13 to dd2ce84 Compare August 18, 2025 19:41
@MateSaary
Copy link
Member Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 18, 2025
Copy link
Member Author

@MateSaary MateSaary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Dee-6777 happy to report that backplane-cli v0.3.0 was released recently, so this PR is now good to go ahead 😄

@MateSaary MateSaary force-pushed the srep-974-describe-node-flag branch from dd2ce84 to 72a5f65 Compare August 19, 2025 12:23
@Makdaam
Copy link
Member

Makdaam commented Aug 19, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2025
@Makdaam
Copy link
Member

Makdaam commented Aug 19, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 19, 2025

@MateSaary: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit c2ca090 into openshift:main Aug 19, 2025
3 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.

4 participants