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

Bastion_test system #322

Closed
o0Ignition0o opened this issue Apr 11, 2021 · 1 comment
Closed

Bastion_test system #322

o0Ignition0o opened this issue Apr 11, 2021 · 1 comment

Comments

@o0Ignition0o
Copy link
Contributor

o0Ignition0o commented Apr 11, 2021

Is your feature request related to a problem? Please describe.

In test settings, It might sometimes be unfortunate to have a SYSTEM that handles all of the bastion lifecycle, especially when we want to isolate tests.

Describe the solution you'd like
The idea would be to have a bastion_test module that would be local to a test, and provide its own init() start() stop() and block_until_stopped() functions, that wouldn't interfere with other tests.

WDYT?

@o0Ignition0o
Copy link
Contributor Author

Closing this because I don't think it's required, as long as we spawn distinct groups and target distinct distributors.

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

No branches or pull requests

1 participant