feat(pipeline): Add Zimmer deployment and lineage step types - #6140
Open
Rishabh0255 wants to merge 1 commit into
Open
feat(pipeline): Add Zimmer deployment and lineage step types#6140Rishabh0255 wants to merge 1 commit into
Rishabh0255 wants to merge 1 commit into
Conversation
Add 8 pipeline step classes for Project Zimmer: - EndpointConfigStep, EndpointStep (SageMaker inference deployment) - InferenceComponentStep (multi-model endpoint support) - BedrockCustomModelStep, BedrockCustomModelDeploymentStep, BedrockModelImportStep, BedrockProvisionedModelThroughputStep - LineageStep (ML governance tracking) Design: each step accepts an opaque 'arguments: Dict[str, Any]' that is passed through to the Tioga service verbatim. This mirrors Tioga's own step definitions in IronmanTiogaPipelineDefinitionRepository — the service validates the Arguments block against the underlying AWS Create*Request model (SageMaker Coral or Bedrock SDK) minus a small exclusion set. The SDK does not duplicate that validation. Excluded fields the service rejects (documented in each step's docstring): EndpointConfig excludes DataCaptureConfig and ExplainerConfig; Endpoint excludes DeploymentConfig; all others: no exclusions. Retryability per Tioga step contract: only EndpointConfigStep is retryable. Cacheability: EndpointConfigStep and EndpointStep are structurally cacheable via cache_config. Bedrock property references use PascalCase field names (matching Tioga's step-property resolver) even though the underlying Bedrock JSON API uses camelCase. sim: https://issues.amazon.com/issues/P424919850 --- X-AI-Prompt: Implement all 8 Zimmer pipeline steps in the Python SDK matching the service's actual accepted Arguments schema (source: Tioga IronmanTiogaPipelineDefinitionRepository) X-AI-Tool: kiro-cli
Rishabh0255
temporarily deployed
to
manual-approval
July 31, 2026 20:57 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Rishabh0255
temporarily deployed
to
manual-approval
July 31, 2026 20:57 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Rishabh0255
temporarily deployed
to
manual-approval
July 31, 2026 20:57 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
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.
Summary
Adds 8 new pipeline step classes for Project Zimmer:
EndpointConfigStep,EndpointStep,InferenceComponentStepBedrockCustomModelStep,BedrockCustomModelDeploymentStep,BedrockModelImportStep,BedrockProvisionedModelThroughputStepLineageStepAlso adds 8 new values to
StepTypeEnumand exports the classes fromsagemaker.mlops.workflow.Design
Each step accepts an opaque
arguments: Dict[str, Any]that is forwarded to the pipeline service verbatim, mirroring the existing SDK convention used byLambdaStepandCallbackStep. Refer to the corresponding AWS API reference (CreateEndpointConfig,CreateEndpoint,CreateInferenceComponent, BedrockCreateCustomModel, etc.) for accepted fields.Retryability follows the Zimmer step contract: only
EndpointConfigStepacceptsretry_policies.EndpointConfigStepandEndpointStepacceptcache_config; nothing else does.Testing
Unit tests (
tests/unit/workflow/test_zimmer_steps.py, 24 tests): construction,to_request()shape, enum values, retry-policy rejection on non-retryable steps, Bedrock properties, LineageStep argument validation.Integration test (
tests/integ/workflow/test_zimmer_lineage_step.py): full end-to-end LineageStep pipeline execution, assertsSucceededand verifies the created action ARN in step metadata.Manual validation performed:
CreatePipeline+DescribePipelineround-trip for all 8 step typesLineageSteppipeline executed toSucceededon gammaCompatibility
No changes to existing step types, no changes to
Pipeline, no changes toStepsCompilerbeyond the enum additions._LocalPipelineExecutioncorrectly rejects the new step types with a clear error message consistent with other unsupported-in-local step types.