Accept PC-assisted Hardware snapshots during robot discovery - #156
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Outcome
Robot discovery and connected-robot configuration now validate PC-assisted Robot Hardware snapshots by their package module and operational scripts. They no longer require the organized Hardware directory to contain Git metadata. Legacy Hardware migration continues to require a recognized legacy Git checkout.
This fixes the post-install error on managed PC-assisted devices:
The organized Hardware package is missing or invalid
Verification
Managed Runtime release decision
No Runtime release is required. This is editor-server SSH discovery/configuration orchestration behind the existing Find and attach robots action and does not alter the managed Runtime bundle or service contract.