fix(dataops-job): apply AmazonDataZoneProject tag so Glue jobs appear in SMUS UI#53
Open
marcinc wants to merge 3 commits into
Open
Conversation
… in SMUS UI Publish the DataZone project ID to SSM from dataops-project-l3-construct so sibling modules can apply the AmazonDataZoneProject tag at deploy time. Read that SSM value in dataops-job-l3-construct and tag each Glue job, making it visible in the SageMaker Unified Studio Build → Visual ETL section. Also add compliance and synth test assertions covering the new tag (positive and negative cases) and the new SSM parameter output in the project construct.
…ect tag on Glue jobs Regenerated CDK diff baselines for all three sample configs (minimal, comprehensive, workertype) to reflect the new AmazonDataZoneProject tag applied to Glue jobs. The tag value is resolved at deploy time from the SSM parameter published by dataops-project and makes jobs visible in the SageMaker Unified Studio project UI.
…ect/id/default SSM parameter Regenerated CDK diff baselines for the comprehensive, datazone, and sagemaker sample configs to reflect the new SSM parameter that publishes the DataZone project ID. This parameter is consumed by sibling modules (dataops-job, dataops-crawler, dataops-workflow) to apply the AmazonDataZoneProject tag, making their resources visible in the SageMaker Unified Studio project UI.
marcinc
force-pushed
the
fix/dataops-job-missing-amazon-datazone-project-tag
branch
from
0459a0a to
3dc0403
Compare
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
1 participant
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: #52
Description of changes:
Publish the DataZone project ID to SSM from
dataops-project-l3-constructso sibling modules can apply theAmazonDataZoneProjecttag at deploy time. Read that SSM value indataops-job-l3-constructand tag each Glue job, making it visible in the SageMaker Unified Studio (Data analytics → Data processing jobs section).Also add compliance and synth test assertions covering the new tag (positive and negative cases) and the new SSM parameter output in the project construct.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.