Repository navigation
Support existing-user endurance tasks and complete-bundle export - #7
Draft
oznetmaster wants to merge 2 commits into
Draft
oznetmaster wants to merge 2 commits into
oznetmaster wants to merge 2 commits into
Conversation
oznetmaster
changed the title
This branch has not been deployed
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.
The endurance scheduler previously supported only LocalService and a connection settings file, forcing existing-user workflows toward unnecessary credential duplication. Add an explicit current-user task option and pinned named-credential bindings so the existing account can use its encrypted processor credential store. Current-user tasks use a limited interactive token and hidden PowerShell; they require the user to remain logged in (locking is supported).
Preserve legacy configurations and LocalService registration. Keep credential bindings outside evidence/CLI directories, verify their hash before collection/export, and exclude the private file from retained snapshots. Clarify that reboot and interruption rehearsals are optional infrastructure validation, not extra Crestron submission criteria.
Completed-run export now accepts pinned CLI files up to 256 MiB, allowing the self-contained setup executable in complete released bundles. Retained evidence remains limited to 64 MiB per file; the 1 GiB inventory limit, complete pin checks, linked-file refusal and source/copy validation remain intact. Precreation failures emit structural diagnostics to stderr without echoing private exception messages or input values.
Validation: 45 synthetic scheduler scenarios, 24 snapshot scenarios and 2 mocked task-identity cases passed. Snapshot regressions include a 127,502,834-byte pinned tool, rejection of altered large tools and oversized tool/evidence files, and precreation diagnostics. No real task registration, credentials or hardware were used in these tests.