Is your feature request related to a problem? Please describe.
get_pipeline_config_and_tar() packages the pipeline config and source code into a tar archive for upload. It is only covered by coverage-only tests that assert nothing meaningful. A bug here would silently produce a corrupt or incomplete archive, causing confusing failures later in the pipeline lifecycle.
Describe the solution you'd like
Add E2E tests that:
- Verify the tar archive contains the expected files with correct contents
- Verify the embedded config YAML is valid and matches the input
- Test with pipelines that have multiple source files and nested directories
- Test error cases: missing files, invalid config YAML, and permission errors
Describe alternatives you've considered
Snapshot testing — compare the tar output to a known-good reference archive. Fast to write but brittle when file contents legitimately change.
Additional context
See python/michelangelo/cli/mactl/plugins/entity/pipeline/create.py:25. This function is on the critical path for every pipeline upload — it needs robust test coverage.
Is your feature request related to a problem? Please describe.
get_pipeline_config_and_tar()packages the pipeline config and source code into a tar archive for upload. It is only covered by coverage-only tests that assert nothing meaningful. A bug here would silently produce a corrupt or incomplete archive, causing confusing failures later in the pipeline lifecycle.Describe the solution you'd like
Add E2E tests that:
Describe alternatives you've considered
Snapshot testing — compare the tar output to a known-good reference archive. Fast to write but brittle when file contents legitimately change.
Additional context
See
python/michelangelo/cli/mactl/plugins/entity/pipeline/create.py:25. This function is on the critical path for every pipeline upload — it needs robust test coverage.