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

Allow SET on nested field where parent is nil #103

Closed
AvitalTamir opened this issue Oct 8, 2024 · 0 comments · Fixed by #113
Closed

Allow SET on nested field where parent is nil #103

AvitalTamir opened this issue Oct 8, 2024 · 0 comments · Fixed by #113
Labels
bug Something isn't working k8s client
Milestone
v0.13

Comments

@AvitalTamir
Copy link
Owner

Currently, SET can only edit a field if it's parent already exists - a common use case is creating a label on a resource that still has no labels.

Currently, the resource must have at least one label for MATCH (x:resource) SET x.metadata.labels.foo="bar" to work.
@AvitalTamir AvitalTamir added bug Something isn't working k8s client labels Oct 8, 2024
@AvitalTamir AvitalTamir changed the title Allow SET on nested field where parent is still nil Allow SET on nested field where parent is nil Oct 8, 2024
@AvitalTamir AvitalTamir added this to the v0.13 milestone Oct 10, 2024
@AvitalTamir AvitalTamir linked a pull request Oct 12, 2024 that will close this issue
fix(k8s-client): allow patching property with nil parent #113
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working k8s client
Projects
None yet
Milestone
v0.13
Development

Successfully merging a pull request may close this issue.

fix(k8s-client): allow patching property with nil parent AvitalTamir/cyphernetes
1 participant
@AvitalTamir