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

chore(topology): Allow internal topologies to be controlled #20286

Closed
wants to merge 1 commit into from

Conversation

bruceg
Copy link
Member

@bruceg bruceg commented Apr 11, 2024

The internal topologies are currently not wrapped by a topology controller. This prevents them from being controlled externally in the case of an early shutdown.

The internal topologies are currently not wrapped by a topology controller. This
prevents them from being controlled externally in the case of an early shutdown.
@bruceg bruceg added domain: topology Anything related to Vector's topology code domain: core Anything related to core crates i.e. vector-core, core-common, etc no-changelog Changes in this PR do not need user-facing explanations in the release changelog labels Apr 11, 2024
@github-actions github-actions bot removed domain: topology Anything related to Vector's topology code domain: core Anything related to core crates i.e. vector-core, core-common, etc labels Apr 11, 2024
@bruceg
Copy link
Member Author

bruceg commented Apr 12, 2024

I discovered an alternate way of handling this, so it's no longer needed.

@bruceg bruceg closed this Apr 12, 2024
@bruceg bruceg deleted the OPA-1336-control-internal-topologies branch April 12, 2024 00:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog Changes in this PR do not need user-facing explanations in the release changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant