Repository navigation
Conversation
nivle1661
temporarily deployed
to
gha-kumo-workflow-tests
November 10, 2026 22:46 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
nivle1661
changed the base branch from
main
to
egu/mlops-platform-integration
November 10, 2026 22:46
nivle1661
temporarily deployed
to
gha-kumo-workflow-tests
November 10, 2026 22:55 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
nivle1661
temporarily deployed
to
gha-kumo-workflow-tests
November 10, 2026 23:34 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
nivle1661
temporarily deployed
to
gha-kumo-workflow-tests
November 11, 2026 00:21 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
nivle1661
temporarily deployed
to
gha-kumo-workflow-tests
November 11, 2026 01:13 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
nivle1661
temporarily deployed
to
gha-kumo-workflow-tests
November 11, 2026 01:22 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
…maker-platform-validation
nivle1661
temporarily deployed
to
gha-kumo-workflow-tests
November 11, 2026 01:24 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
…maker-platform-validation
nivle1661
temporarily deployed
to
gha-kumo-workflow-tests
November 11, 2026 01:40 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
nivle1661
had a problem deploying
to
gha-kumo-workflow-tests
November 11, 2026 02:03 — with
GitHub Actions
Error
GitHub Actions
Error
nivle1661
temporarily deployed
to
gha-kumo-workflow-tests
November 11, 2026 02:04 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
…maker-platform-validation
This branch was successfully 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.
Summary
Add SageMaker NotebookJobStep execution and native managed MLflow/Studio UI checks on the shared harness from #239. Reuse the small two-fit lifecycle and graph fixture for versions, aliases, reload/predict, lineage, tracking, monitoring, permission denial, graph controls, sample safeguards, saved outputs and exports.
Build the dispatched revision’s wheel and use shared wheel identity admission. Require a dedicated environment-only OIDC runner with separate bounded pipeline/runtime roles, clean attempt-owned resources, generate one guarded standalone admin migration, and upload aggregate results only.
Change map
Maintained change map
Testing Done
The local offline seven-suite run passed 229 tests, with no skips, after reproducing and fixing a clean-runner Playwright import failure. The URL guard regression now rejects any Playwright load even when dependencies are cached locally. The earlier complete eight-suite run passed 317 tests. Independent review, lint/import ordering, Node syntax, signed commits and product-tree equality with #239 passed. All seven historical raw SageMaker artifacts were deleted and verified unavailable (HTTP 404).
The GitHub environment prevents self-review. Automatic platform-regression CI coverage is deferred to a separate follow-up. The manual cloud workflow and local regression commands remain available. Runner-role deployment and dedicated-role live qualification need outside help and are excluded from this iteration at the user’s request; existing role/policy source is retained.