Skip to content

NO-ISSUE: Add a slash command creating a Sushy resource from Schema#136

Open
jacob-anders wants to merge 2 commits into
openshift:mainfrom
jacob-anders:slash-cmd-resource-from-schema
Open

NO-ISSUE: Add a slash command creating a Sushy resource from Schema#136
jacob-anders wants to merge 2 commits into
openshift:mainfrom
jacob-anders:slash-cmd-resource-from-schema

Conversation

@jacob-anders

@jacob-anders jacob-anders commented Dec 24, 2025 •
edited
Loading

Copy link
Copy Markdown

Sample Cursor/Claude command:

/generate-sushy-resource ./redfish/v1/Schemas/SoftwareInventory.v1_9_0.json/index.json

Sample output:

https://paste.openstack.org/show/b3k5cspq8MKMqVd2hpYD/

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 24, 2025
@openshift-ci-robot

openshift-ci-robot commented Dec 24, 2025

Copy link
Copy Markdown

@rhjanders: This pull request explicitly references no jira issue.

Details

In response to this:

Sample Cursor/Claude command:

/generate-sushy-resource ./redfish/v1/Schemas/SoftwareInventory.v1_9_0.json/index.json

Sample output:

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 requested review from iurygregory and zaneb December 24, 2025 08:53
@openshift-ci

openshift-ci Bot commented Dec 24, 2025

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhjanders

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 Dec 24, 2025
@jacob-anders jacob-anders changed the title NO-ISSUE: Slash cmd resource from schema NO-ISSUE: Add a slash command creating a Sushy resource from Schema Dec 24, 2025
@jacob-anders
Add a slash command creating a Sushy resource from Schema
1a6658a 
Assisted-By: Claude Code Sonnet 4.5
Signed-off-by: Jacob Anders <janders@redhat.com>
@jacob-anders jacob-anders force-pushed the slash-cmd-resource-from-schema branch from 5932a39 to 1a6658a Compare December 24, 2025 09:57
@openshift-ci

openshift-ci Bot commented Dec 24, 2025

Copy link
Copy Markdown

@rhjanders: 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.

@jacob-anders

jacob-anders commented Dec 24, 2025

Copy link
Copy Markdown
Author

another test against DMTF hosted file:

/generate-sushy-resource https://redfish.dmtf.org/schemas/v1/SoftwareInventory.v1_13_0.json

https://paste.openstack.org/show/bVzPRxFKJCLUNlxiONjl/

@elfosardo

elfosardo commented Dec 29, 2025

Copy link
Copy Markdown

/hold

@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 Dec 29, 2025
@iurygregory

iurygregory commented Dec 29, 2025

Copy link
Copy Markdown

@elfosardo just to check, but why we need to hold?

@elfosardo

elfosardo commented Dec 30, 2025

Copy link
Copy Markdown

@iurygregory I thought I added the reason, sorry!
Mainly because this is a downstream repo and we don't add anything here if not backports/cherry-picks/syncs
I would like for this to go upstream instead

@openshift-bot

openshift-bot commented Mar 31, 2026

Copy link
Copy Markdown

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 31, 2026
@openshift-bot

openshift-bot commented Apr 30, 2026

Copy link
Copy Markdown

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@iurygregory iurygregory Awaiting requested review from iurygregory

@zaneb zaneb Awaiting requested review from zaneb

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@jacob-anders @openshift-ci-robot @elfosardo @iurygregory @openshift-bot