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

Set ConnectedState(s) to ATTEMPTING after a PUT/PATCH request for a connection #256

Open
shouples opened this issue Dec 23, 2024 · 0 comments · May be fixed by #257
Open

Set ConnectedState(s) to ATTEMPTING after a PUT/PATCH request for a connection #256

shouples opened this issue Dec 23, 2024 · 0 comments · May be fixed by #257

Comments

@shouples
Copy link
Contributor

In the case of DIRECT connection types, we could run into the following scenarios when changing the underlying configurations that may cause the connected state to transition from:

  • SUCCESS to FAILED (invalid credentials or bootstrap servers / SR URI)
  • FAILED to SUCCESS (valid credentials or bootstrap servers / SR URI)

Currently, the sidecar returns the last known ConnectedState(s) until the next async status check happens, so a GET request immediately after a PUT/PATCH request may return stale information.
@rohitsanj rohitsanj linked a pull request Dec 23, 2024 that will close this issue
Open
5 tasks
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

Successfully merging a pull request may close this issue.

Reset to initial connection state on connection update confluentinc/ide-sidecar
1 participant
@shouples