-
Notifications
You must be signed in to change notification settings - Fork 60
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
openstack client: include TenantID in list options #6156
openstack client: include TenantID in list options #6156
Conversation
…ks and SubnetPools
/hold I need an opinion from someone with more openstack experience. Maybe there is a use case for listing networks, SGs and security groups that are not correlated with a project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
LGTM label has been added. Git tree hash: 1161c45a791184a1ea3982edf4f3457143e3ba3e
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik, pkprzekwas 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 |
/hold cancel |
/retest |
/cherrypick release/v2.23 |
@pkprzekwas: new pull request created: #6200 In response to this:
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/test-infra repository. |
What this PR does / why we need it:
If openstack user configured in credentials is an admin, our API lists all the networks, security groups and subnet pools that user has access to without filtering by provided ProjectID/ProjectName. This PR introduces additional filtering for networks, security groups and subnet pools listings.
What type of PR is this?
/kind bug
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: