resource scope potential 1 - for #194 #199
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clux
force-pushed
the
resource-scope-arnav1
branch
from
a82edba to
e9cad9f
Compare
it currently just makes things worse because the traits doesn't provide any information, so leaving it in here. i like the api though.
clux
referenced
this pull request
in nightkr/kube-rs
Jul 25, 2020
Fixes kube-rs#293. This is a bit magical, but it's fairly common in K8s to allow reference fields (such as `OwnerReferences`) to refer to either cluster-scoped objects or namespaced resources in the same namespace. Code that converts those events into `ObjectRef`s generally won't know which of these cases is applicable, so this is the best we can do.
|
Superseded by #956 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tries the first of Arnavion's potentials via Arnavion/k8s-openapi#65 (comment)
It's assumed that k8s-openapi actually fills in these traits rather than me inlining them, but this is for our tests/experimentation atm.
I don't see a good way to get compile time prevention of using
Api::createif you're inside aResource::allview, but we can at least assert here. Not bad at all.