-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Fix cannot get registered resource #5515
Conversation
Signed-off-by: wenhaozhou <wenhaozhou@yunify.com>
/cc @wansir |
lgtm @wansir |
LGTM label has been added. Git tree hash: 54a7c37ad4eee68e5ba875fd04afc26752f12a6d
|
Signed-off-by: wenhaozhou <wenhaozhou@yunify.com>
/unhold |
/lgtm |
LGTM label has been added. Git tree hash: 333f65524aa3eebc6a3db5227bcea873c547edf6
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wansir, zhou1203 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 |
* Fix can`t get registered resource Signed-off-by: wenhaozhou <wenhaozhou@yunify.com> * update v1beta1 interface Get func`s parameters Signed-off-by: wenhaozhou <wenhaozhou@yunify.com> --------- Signed-off-by: wenhaozhou <wenhaozhou@yunify.com>
* Fix can`t get registered resource Signed-off-by: wenhaozhou <wenhaozhou@yunify.com> * update v1beta1 interface Get func`s parameters Signed-off-by: wenhaozhou <wenhaozhou@yunify.com> --------- Signed-off-by: wenhaozhou <wenhaozhou@yunify.com>
* Fix can`t get registered resource Signed-off-by: wenhaozhou <wenhaozhou@yunify.com> * update v1beta1 interface Get func`s parameters Signed-off-by: wenhaozhou <wenhaozhou@yunify.com> --------- Signed-off-by: wenhaozhou <wenhaozhou@yunify.com> (cherry picked from commit b143b41)
Signed-off-by: wenhaozhou wenhaozhou@yunify.com
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: