Skip to content

SREP-21: backplane API is now allocating a remediation instance id for each call to createRemediation #19

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

Merged
merged 1 commit into from
May 14, 2025

Conversation

Nikokolas3270
Copy link
Contributor

@Nikokolas3270 Nikokolas3270 commented Apr 30, 2025

What type of PR is this?

feature

What this PR does / Why we need it?

This new id is used at deletion time (deleteRemediation) to locate the SA & RBAC to delete.
This allows to call createRemediation several times with the same remediation name and not mix up the resources created on the target cluster for each call.

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

_Contributes to SREP-21

Special notes for your reviewer

Other PR will follows on backplane-cli and on the other (gitlab) backplane-api repo.
Lastly CAD will be changed to support & use this new API

Pre-checks (if applicable)

  • Generated new-client-pkg
  • Included documentation changes with PR

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

openshift-ci-robot commented Apr 30, 2025

@Nikokolas3270: This pull request references SREP-21 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 bug to target the "4.19.0" version, but no target version was set.

In response to this:

What type of PR is this?

feature

What this PR does / Why we need it?

This new id is used at deletion time (deleteRemediation) to locate the SA & RBAC to delete.
This allows to call createRemediation several times with the same remediation name and not mix up the resources created on the target cluster for each call.

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

_Contributes to SREP-21

Special notes for your reviewer

Other PR will follows on backplane-cli and on the other (gitlab) backplane-api repo.
Lastly CAD will be changed to support & use this new API

Pre-checks (if applicable)

  • Generated new-client-pkg
  • 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 requested review from feichashao and Tafhim April 30, 2025 10:01
@Nikokolas3270 Nikokolas3270 force-pushed the SREP-21 branch 2 times, most recently from 1dd56a7 to 73b8e29 Compare April 30, 2025 11:15
…n calling createRemediation; this id will be used in place of the remediation name at deleteRemediation time.

This will allow backplane to have several remediations with the same name in parallel without mixing up the resources created on the target cluster.
Copy link
Contributor

openshift-ci bot commented Apr 30, 2025

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

@RaphaelBut
Copy link
Contributor

It looks good to me.

@iamkirkbater
Copy link

LGTM

@samanthajayasinghe
Copy link

/lgtm

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

/lgtm
/approve

@feichashao
Copy link

/approve

Copy link
Contributor

openshift-ci bot commented May 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: feichashao, MitaliBhalla, Nikokolas3270, samanthajayasinghe

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 May 14, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 2aa5755 into openshift:main May 14, 2025
2 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.

7 participants