-
Notifications
You must be signed in to change notification settings - Fork 3.1k
feat(onboard): add managed shared-state transactions #7962
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
Closed
ericksoa
wants to merge
6
commits into
feat/buildless-managed-image-application
from
feat/buildless-shared-state-transactions
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
06f67e5
feat(onboard): add managed shared-state transactions
ericksoa f3081cc
chore(stack): restack PR3.5 on PR3.4b
ericksoa 51126c4
chore(stack): carry PR3.4b guardrail fix into PR3.5
ericksoa 0edd158
chore(stack): restack PR3.5 after PR3.3 merge
ericksoa b2027a9
feat(onboard): add managed shared-state transactions
ericksoa b1726a6
feat(onboard): add managed shared-state transactions
ericksoa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
The CA-leak assertion cannot fail.
writeCompletionFixturebuilds the runtime environment string itself at Line 507. It passes onlymapped.runtimeEnvironmentandmapped.configurationEnvironment. The corporate CA base64 never enters that input, because the profile carries onlycorporateCa.bundleSha256. The assertion at Line 631 therefore checks the fixture, not the production write path atimage-runtime.tsLine 1381.Assert the property through the public boundary instead. Apply a profile that carries a corporate CA through
applyManagedStartupRootRequestwithcorporateCaB64set, then read the written runtime environment file. Alternatively, narrow the test title to the completion-marker claim it does verify.As per path instructions: "Prefer observable outcomes through the public boundary over source-text, private-shape, or mock-call assertions" and "Flag ... conditionals that make a test pass without exercising its claim."
🧰 Tools
🪛 ast-grep (0.45.0)
[warning] 630-630: Filesystem path is not a string literal; a request-/variable-derived path can enable path traversal. Validate and normalize the path before use.
Context: fs.readFileSync(fixture.runtimeEnvironmentFile, "utf8")
Note: [CWE-22] Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
(detect-non-literal-fs-filename-typescript)
🤖 Prompt for AI Agents
Source: Path instructions