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

chore: Update vm-console-proxy to v0.5.0 #916

Merged
merged 2 commits into from
Mar 13, 2024

Conversation

akrejcir
Copy link
Collaborator

@akrejcir akrejcir commented Mar 7, 2024

What this PR does / why we need it:
Updated vm-console-proxy to version v0.5.0, and changed code to support multiple ClusterRoles.

Release note:

Updated vm-console-proxy to version v0.5.0.

Signed-off-by: Andrej Krejcir <akrejcir@redhat.com>
@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Mar 7, 2024
@kubevirt-bot kubevirt-bot requested review from 0xFelix and ksimon1 March 7, 2024 14:15
@akrejcir
Copy link
Collaborator Author

akrejcir commented Mar 7, 2024

/cc @0xFelix @ksimon1

@@ -142,5 +144,10 @@ func validateBundle(bundle *Bundle) error {
if len(missingFields) > 0 {
return fmt.Errorf("bundle is missing these objects: %v", missingFields)
}

if len(bundle.ClusterRoles) != 2 {
Copy link
Member

Choose a reason for hiding this comment

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

Do we need to hardcode this check here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

No. I wanted to be explicit, that there should be 2 roles.
I will make the code more generic.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I've just removed the condition. Making the code more generic is maybe a task for a future PR.

@akrejcir akrejcir force-pushed the update-vm-console-proxy branch from cc00fbe to 6044bd7 Compare March 8, 2024 14:24
Copy link
Member

@0xFelix 0xFelix left a comment

Choose a reason for hiding this comment

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

/approve

Thanks looks good to me.

@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 0xFelix

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 11, 2024
@akrejcir
Copy link
Collaborator Author

/retest

The latest vm-console-proxy contains a new cluster role.

Signed-off-by: Andrej Krejcir <akrejcir@redhat.com>
@akrejcir akrejcir force-pushed the update-vm-console-proxy branch from 6044bd7 to ef0be76 Compare March 12, 2024 13:13
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@akrejcir
Copy link
Collaborator Author

/cc @jcanocan

@kubevirt-bot kubevirt-bot requested a review from jcanocan March 13, 2024 10:32
@jcanocan
Copy link
Contributor

Great work @akrejcir !
/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 13, 2024
@kubevirt-bot kubevirt-bot merged commit 9426a16 into kubevirt:main Mar 13, 2024
11 of 12 checks passed
@akrejcir akrejcir deleted the update-vm-console-proxy branch March 13, 2024 11:47
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants