Add CSP configuration validation to SageMaker build workflow #70
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.
Issue #, if available:
D322618311
Description of changes:
Description
Adds CSP (Content Security Policy) configuration validation to the build workflow for the
code-editor-sagemaker-servertarget.Changes
.github/workflows/build-targets.yamlcode-editor-sagemaker-servertargetTesting
Remote
Ran build-target github action two times, before and after modifying 'patches/sagemaker/update-csp.diff', which changes CSP text.
Received one success and one failure outcome, as expected.
Link:
https://github.com/feiyangliu2023/code-editorv2/actions/runs/18529763981
https://github.com/feiyangliu2023/code-editorv2/actions/runs/18531210588
Local
Created two test scripts to verify both success and failure scenarios:
Success:
code-editor-sagemaker-serverFaiure:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.