control-plane: move auto-discovers into controllers #1585
Assignees
Comments
psFried
added a commit
that referenced
this issue
Nov 8, 2024
Fixes #1674 and #1585 Implements auto-discovers as part of capture controllers. This gives auto-discovers their own status, and generally makes it easier to debug auto-discover issues and see what's happening. In order to make this work, discovers were significalntly refactored, and given a similar treatment to publications and evolutions. It is now possible to discover into an in-memory `tables::DraftCatalog`, which will be used as the merge base. Discovers now return a structured summary of modifications, similar to publications and evolutions. This summary is stored as part of the auto-discover status. The discover merge logic was updated to always add all discovered bindings, regardless of the `update_only` flag. If `update_only` is true, then the new bindings will be disabled.
psFried
added a commit
that referenced
this issue
Nov 8, 2024
Fixes #1674 and #1585 Implements auto-discovers as part of capture controllers. This gives auto-discovers their own status, and generally makes it easier to debug auto-discover issues and see what's happening. In order to make this work, discovers were significalntly refactored, and given a similar treatment to publications and evolutions. It is now possible to discover into an in-memory `tables::DraftCatalog`, which will be used as the merge base. Discovers now return a structured summary of modifications, similar to publications and evolutions. This summary is stored as part of the auto-discover status. The discover merge logic was updated to always add all discovered bindings, regardless of the `update_only` flag. If `update_only` is true, then the new bindings will be disabled.
psFried
added a commit
that referenced
this issue
Nov 11, 2024
Fixes #1674 and #1585 Implements auto-discovers as part of capture controllers. This gives auto-discovers their own status, and generally makes it easier to debug auto-discover issues and see what's happening. In order to make this work, discovers were significalntly refactored, and given a similar treatment to publications and evolutions. It is now possible to discover into an in-memory `tables::DraftCatalog`, which will be used as the merge base. Discovers now return a structured summary of modifications, similar to publications and evolutions. This summary is stored as part of the auto-discover status. The discover merge logic was updated to always add all discovered bindings, regardless of the `update_only` flag. If `update_only` is true, then the new bindings will be disabled.
psFried
added a commit
that referenced
this issue
Nov 11, 2024
Fixes #1674 and #1585 Implements auto-discovers as part of capture controllers. This gives auto-discovers their own status, and generally makes it easier to debug auto-discover issues and see what's happening. In order to make this work, discovers were significalntly refactored, and given a similar treatment to publications and evolutions. It is now possible to discover into an in-memory `tables::DraftCatalog`, which will be used as the merge base. Discovers now return a structured summary of modifications, similar to publications and evolutions. This summary is stored as part of the auto-discover status. The discover merge logic was updated to always add all discovered bindings, regardless of the `update_only` flag. If `update_only` is true, then the new bindings will be disabled.
psFried
added a commit
that referenced
this issue
Nov 11, 2024
Fixes #1674 and #1585 Implements auto-discovers as part of capture controllers. This gives auto-discovers their own status, and generally makes it easier to debug auto-discover issues and see what's happening. In order to make this work, discovers were significalntly refactored, and given a similar treatment to publications and evolutions. It is now possible to discover into an in-memory `tables::DraftCatalog`, which will be used as the merge base. Discovers now return a structured summary of modifications, similar to publications and evolutions. This summary is stored as part of the auto-discover status. The discover merge logic was updated to always add all discovered bindings, regardless of the `update_only` flag. If `update_only` is true, then the new bindings will be disabled.
psFried
added a commit
that referenced
this issue
Nov 11, 2024
Fixes #1674 and #1585 Implements auto-discovers as part of capture controllers. This gives auto-discovers their own status, and generally makes it easier to debug auto-discover issues and see what's happening. In order to make this work, discovers were significalntly refactored, and given a similar treatment to publications and evolutions. It is now possible to discover into an in-memory `tables::DraftCatalog`, which will be used as the merge base. Discovers now return a structured summary of modifications, similar to publications and evolutions. This summary is stored as part of the auto-discover status. The discover merge logic was updated to always add all discovered bindings, regardless of the `update_only` flag. If `update_only` is true, then the new bindings will be disabled.
psFried
added a commit
that referenced
this issue
Nov 11, 2024
Fixes #1674 and #1585 Implements auto-discovers as part of capture controllers. This gives auto-discovers their own status, and generally makes it easier to debug auto-discover issues and see what's happening. In order to make this work, discovers were significalntly refactored, and given a similar treatment to publications and evolutions. It is now possible to discover into an in-memory `tables::DraftCatalog`, which will be used as the merge base. Discovers now return a structured summary of modifications, similar to publications and evolutions. This summary is stored as part of the auto-discover status. The discover merge logic was updated to always add all discovered bindings, regardless of the `update_only` flag. If `update_only` is true, then the new bindings will be disabled.
psFried
added a commit
that referenced
this issue
Nov 12, 2024
Fixes #1674 and #1585 Implements auto-discovers as part of capture controllers. This gives auto-discovers their own status, and generally makes it easier to debug auto-discover issues and see what's happening. In order to make this work, discovers were significalntly refactored, and given a similar treatment to publications and evolutions. It is now possible to discover into an in-memory `tables::DraftCatalog`, which will be used as the merge base. Discovers now return a structured summary of modifications, similar to publications and evolutions. This summary is stored as part of the auto-discover status. The discover merge logic was updated to always add all discovered bindings, regardless of the `update_only` flag. If `update_only` is true, then the new bindings will be disabled.
psFried
added a commit
that referenced
this issue
Nov 12, 2024
Fixes #1674 and #1585 Implements auto-discovers as part of capture controllers. This gives auto-discovers their own status, and generally makes it easier to debug auto-discover issues and see what's happening. In order to make this work, discovers were significalntly refactored, and given a similar treatment to publications and evolutions. It is now possible to discover into an in-memory `tables::DraftCatalog`, which will be used as the merge base. Discovers now return a structured summary of modifications, similar to publications and evolutions. This summary is stored as part of the auto-discover status. The discover merge logic was updated to always add all discovered bindings, regardless of the `update_only` flag. If `update_only` is true, then the new bindings will be disabled.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: