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.

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

Reset to initial connection state on connection update #257

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

rohitsanj
Copy link
Contributor

Summary of Changes

Resolves #256

Any additional details or context that should be provided?

Pull request checklist

Please check if your PR fulfills the following (if applicable):

  • Tests:
    • Added new
    • Updated existing
    • Deleted existing
  • Have you validated this change locally against a running instance of the Quarkus dev server?
    make quarkus-dev
  • Have you validated this change against a locally running native executable?
    make mvn-package-native && ./target/ide-sidecar-*-runner

@rohitsanj rohitsanj requested a review from a team as a code owner December 23, 2024 22:26
@sonarqube-confluent

This comment has been minimized.

@sonarqube-confluent
Copy link

Passed

Analysis Details

0 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 0 Code Smells

Coverage and Duplications

  • Coverage 100.00% Coverage (80.40% Estimated after merge)
  • Duplications No duplication information (0.60% Estimated after merge)

Project ID: ide-sidecar

View in SonarQube

@@ -107,6 +107,8 @@ default String sidecarUri(String endpointPath) {

Connection createConnection(ConnectionSpec spec);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would we ever not want to reset on connection update?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe updating name or id perhaps shouldn't reset the connection status, but we don't want to introduce complex conditionals ("did id change? do this else that") and instead just reset if any part of the ConnectionSpec changes. Either way, the scheduled refresh of the connection status will keep us eventually up-to-date.

@Cerchie Cerchie self-requested a review December 24, 2024 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Set ConnectedState(s) to ATTEMPTING after a PUT/PATCH request for a connection
2 participants