fix: improve ssh config logic when workspaces change #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
previously, ssh reconfiguration was triggered only when new workspaces were added, and
the ssh config was generated only with the additional environments removing the configuration
for the previous ones. This means that when a new workspace is created from the web dashboard,
the old workspaces are no longer accessible via ssh from Toolbox
now, the logic ensures ssh reconfiguration happens whenever the set of environments changes
(including additions or removals), making it more robust, and configuration happens for all
valid workspaces.
resolves Can't connect to an existing and running workspace after a new one was created from the web dashboard #14