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.

Sign up for GitHub

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

Jump to bottom

filepath does not implement rest.Scoper #549

Closed
drewwells opened this issue Oct 20, 2020 · 4 comments
Closed

filepath does not implement rest.Scoper #549

drewwells opened this issue Oct 20, 2020 · 4 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@drewwells
Copy link
Contributor

error in registering resource: contacts, "burger" must implement scoper

The storage backend has to implement rest.Scoper
drewwells added a commit to infobloxopen/apiserver-builder-alpha that referenced this issue Oct 20, 2020
@drewwells
implement rest.Scoper, return filesystem errors fixes kubernetes-sigs…
f5f1deb 
…#549
@k8s-ci-robot k8s-ci-robot mentioned this issue Oct 20, 2020
Merged
drewwells added a commit to infobloxopen/apiserver-builder-alpha that referenced this issue Oct 20, 2020
@drewwells
implement rest.Scoper
9e55862 
return filesystem errors

fixes kubernetes-sigs#549
drewwells added a commit to infobloxopen/apiserver-builder-alpha that referenced this issue Oct 22, 2020
@drewwells
implement rest scoper
7969a13 
return filesystem errors

fixes kubernetes-sigs#549
drewwells added a commit to infobloxopen/apiserver-builder-alpha that referenced this issue Oct 22, 2020
@drewwells
implement rest scoper kubernetes-sigs#549
c49fd70 
return filesystem errors
drewwells added a commit to infobloxopen/apiserver-builder-alpha that referenced this issue Oct 22, 2020
@drewwells
implement rest scoper kubernetes-sigs#549
0dd964a 
return filesystem errors
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 18, 2021
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 17, 2021
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@drewwells @k8s-ci-robot @fejta-bot