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

Backport of CSI: fix prefix queries for plugin status into release/1.1.x #12674

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #12194 to be assessed for backporting due to the inclusion of the label backport/1.1.x.

The below text is copied from the body of the original PR.


The CSIPlugin.List RPC was intended to accept a prefix to filter the
list of plugins being listed. This was being accidentally being done
in the state store instead, which contributed to incorrect filtering
behavior for plugins in the volume plugin status command.

Move the prefix matching into the RPC so that it calls the
prefix-matching method in the state store if we're looking for a
prefix.

Update the plugin status command to accept a prefix for the plugin
ID argument so that it matches the expected behavior of other commands.


I pulled this out of #12193 because this will need to be backported, whereas not everything in that PR should be.

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/csi-plugin-list-filtering/lightly-more-gazelle branch from 4e7a27e to e7434b2 Compare April 19, 2022 18:37
@hc-github-team-nomad-core hc-github-team-nomad-core merged commit 4ab2729 into release/1.1.x Apr 19, 2022
@hc-github-team-nomad-core hc-github-team-nomad-core deleted the backport/csi-plugin-list-filtering/lightly-more-gazelle branch April 19, 2022 18:37
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants