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

Key deletion doesn't unblock a watch #213

Closed
evanphx opened this issue Jun 13, 2014 · 1 comment
Closed

Key deletion doesn't unblock a watch #213

evanphx opened this issue Jun 13, 2014 · 1 comment

Comments

@evanphx
Copy link
Contributor

evanphx commented Jun 13, 2014

Given /a/x and /a/y, issuing a watch on /a and the deleting /a/x doesn't unblock the watch with information about the deletion. If /a/y is then deleted, the watch is unblocked and returns a 404.
@armon
Copy link
Member

armon commented Jun 13, 2014

Duplicate of #195. This is a known issue with nested deletes.

@armon armon closed this as completed Jun 13, 2014
duckhan pushed a commit to duckhan/consul that referenced this issue Oct 24, 2021
@lkysow
Ensure caBundle is set to string
1b64403 
Without this change, we output:
      caBundle:
when .Values.connectInject.certs.caBundle is empty instead of
      caBundle: ""

I can't reproduce the issue (hashicorp#213) however I'm guessing this may be the
cause if Kubernetes is treating this as null instead of the empty
string.
@wangleo61 wangleo61 mentioned this issue Jul 5, 2023
Open
@terrorizer1980 terrorizer1980 mentioned this issue Jul 6, 2023
Open
@terrorizer1980 terrorizer1980 mentioned this issue Nov 28, 2023
Open
@qmutz qmutz mentioned this issue Nov 29, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@evanphx @armon