feat(k8s): allow container name overriding in PipelineStep#254
Open
feat(k8s): allow container name overriding in PipelineStep#254
Conversation
Adds an optional `container_name` field to `PipelineStepContext` that lets callers override the default `pipeline-consumer` container name in generated Kubernetes deployments. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨
Internal Changes 🔧Deps
🤖 This preview updates automatically when you update the PR. |
evanh
approved these changes
Mar 13, 2026
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
2 participants
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
container_namefield toPipelineStepContext(defaults topipeline-consumer)parse_context(),build_container(), andPipelineStep.run()Test plan
test_build_container_custom_name— verifiesbuild_container()uses the provided nametest_run_custom_container_name— verifies the fullPipelineStep.run()flow respectscontainer_name🤖 Generated with Claude Code