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 individual interfaces to be "disconnect mode" #676

Closed
ghost opened this issue Dec 4, 2017 · 0 comments · Fixed by #730
Closed

Allow individual interfaces to be "disconnect mode" #676

ghost opened this issue Dec 4, 2017 · 0 comments · Fixed by #730
Labels
Milestone

Comments

@ghost
Copy link

ghost commented Dec 4, 2017

During initial configuration of a system it is common to not have all the required hardware available. As hardware arrives some interfaces become real while others need to be stubbed or simply don't exist. It would be nice for script development if the real interfaces could really interact with hardware while other interfaces could act similar to how the script "disconnect mode" operates. Perhaps a new keyword under an INTERFACE called DISCONNECT or SIMULATOR_MODE or something. We would have to ensure that there is visual distinction to the user to indicate this mode is being used so there isn't confusion if this mode is accidentally enabled.

@ghost ghost added the feature label Dec 4, 2017
@ghost ghost self-assigned this Mar 8, 2018
@ghost ghost mentioned this issue Mar 8, 2018
@ghost ghost closed this as completed in #730 Apr 2, 2018
@ghost ghost added this to the v4.2.2 milestone Apr 11, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants