-
Notifications
You must be signed in to change notification settings - Fork 336
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
chore(*) handle resources that are global scoped #1127
Conversation
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
@@ -10,6 +10,9 @@ import ( | |||
|
|||
const ( | |||
DefaultMesh = "default" | |||
// NoMesh defines a marker that resource is not bound to a Mesh. | |||
// Resources not bound to a mesh (ScopeGlobal) should have an empty string in Mesh field. | |||
NoMesh = "" |
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.
hmm, can we use some special character/string instead? Not sure if "" is the universal way to designate NoMesh. How is this encoded in YAML/JSON?
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.
"Not sure if "" is the universal way to designate NoMesh " Hm, why not?
When string is empty, mesh field is excluded from the JSON/YAML.
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.
I like it. Have a couple of small remarks only.
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.
Overall looks great! Just a couple of comments that might improve the store's user experience
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
Summary
This PR fixes the fact that Zone is bound to a Mesh.
We have two resources that are not abound to a mesh - Zone and Mesh.
Our core resources has
mesh
field in all resources.Before this PR:
mesh
field withname
fielddefault
in amesh
. We cannot do this, because Zone is not really bound to a Mesh and default Mesh may not be even in the system.With this PR:
mesh
field if resource is of ScopeGlobalFull changelog
mesh
is emptyIssues resolved
Fix #1023
Documentation