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

Allow fallback to local bindings server if remote is down #1765

Open
krzema12 opened this issue Jan 11, 2025 · 3 comments
Open

Allow fallback to local bindings server if remote is down #1765

krzema12 opened this issue Jan 11, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@krzema12
Copy link
Member

krzema12 commented Jan 11, 2025

Problem

We've recently had an incident where the bindings server under https://bindings.krzeminski.it/ was down or unstable. Because of this, the users experienced CI failures and couldn't develop the workflows.

Proposed approach

Let's add a mode where the logic detects that the remote server is down, and a local instance of the server is started. To start with, it should be an opt-in feature, but in the longer run, we can make it the default behavior.

Let's build a PoC first: #1766

@krzema12 krzema12 added the enhancement New feature or request label Jan 11, 2025
@krzema12 krzema12 self-assigned this Jan 11, 2025
@krzema12
Copy link
Member Author

@krzema12
Copy link
Member Author

Here's a feature that would let the users mitigate the problem only for the consistency check jobs (running on CI): #1767

@krzema12
Copy link
Member Author

Leaving open to remember about at least trying to cover other cases, like:

  • local development - recommend starting the service locally
  • CI checks that run consistency check for all existing workflows, also e.g. schedule-based

@krzema12 krzema12 removed their assignment Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant