Skip to content

Dockpipe Version 0.6.0 Release - #4

Open
jamie-steele wants to merge 472 commits into
masterfrom
staging
Open

Dockpipe Version 0.6.0 Release#4
jamie-steele wants to merge 472 commits into
masterfrom
staging

Conversation

@jamie-steele

Copy link
Copy Markdown
Owner

No description provided.

Jamie Steele added 30 commits April 18, 2026 15:45
…orkPipe codebase; enhance Pipeon dev stack scripts and Docker configuration
…; enhance Docker build skipping logic and related tests
- Updated `dockpipe runs` command usage to include policy record inspection.
- Added validation for network enforcement modes in `ValidateCompiledSecurityPolicy`.
- Introduced tests for new validation rules regarding network policies.
- Expanded `Workflow` struct to include compose and security configurations.
- Implemented `RunComposeLifecycle` to manage Docker Compose commands.
- Created `RunPolicyRecord` structure for managing runtime policy records.
- Added functionality to write and list run policy records.
- Enhanced tests to cover new features and validation rules.
- Updated documentation in capabilities.md to clarify the role of capabilities and resolvers in workflow authoring.
- Expanded CLI reference in cli-reference.md to highlight key flags for workflow execution, including `--workflow`, `--runtime`, and `--resolver`.
- Revised workflow YAML documentation to introduce a recommended mental model for users, emphasizing the importance of steps, runtime, and resolver.
- Modified existing workflows (run, run-apply, run-apply-validate) to explicitly set the runtime to `dockerimage`.
- Implemented changes in the workflow initialization process to prefer `resolver` and `runtime` fields over deprecated `default_*` fields.
- Updated the application logic to support the new `workflow` and `package` fields for packaged workflows, ensuring proper validation and execution.
- Enhanced tests to validate the new packaged workflow structure and ensure backward compatibility with existing configurations.
- Adjusted the workflow schema to include definitions for the new `workflow` and `package` fields in step configurations.
…kind: host`

- Updated all instances of `skip_container` in workflow steps to use `kind: host` for clarity and consistency.
- Modified related test cases and validation logic to accommodate the new step definition.
- Removed deprecated fields and validation checks for `capability`, `default_runtime`, and `default_resolver`.
- Enhanced workflow schema to reflect the removal of obsolete fields and added validation for `kind`.
- Adjusted documentation and comments to align with the new workflow structure.
- Added `security` field to workflow YAML to define container security policies, including network, filesystem, and process settings.
- Updated onboarding and package model documentation to reflect new security policy structure.
- Modified runtime artifact compilation to incorporate security profiles and sources.
- Enhanced validation logic to reject unknown security profiles and enforce rules for allowlist and offline modes.
- Updated tests to cover new security policy features and ensure correct behavior.
…handling

- Refactor `writeCompiledWorkflowRuntimeArtifacts` to include step artifacts and handle their writing.
- Introduce `compiledStepRuntimeArtifacts` type to manage step-specific runtime artifacts.
- Update `compileWorkflowRuntimeArtifacts` to return step artifacts alongside the main runtime manifest and image artifact.
- Implement `compileStepRuntimeArtifacts` and `compileStepRuntimeManifest` for detailed step-level artifact compilation.
- Modify `maybeSkipDockerBuildForStep` and related functions to accommodate step-specific policy fingerprints.
- Add functions to load compiled runtime and image artifacts for individual steps.
- Enhance proxy policy handling in `applyCompiledProxyNetworkPolicy` to include tokenized proxy URLs.
- Introduce a new policy proxy server script to enforce network policies based on compiled proxy configurations.
- Update tests to reflect changes in function signatures and ensure proper handling of step artifacts and proxy policies.
- Introduced `image` field in package metadata to specify OCI image references.
- Updated compilation process to handle image metadata and integrate it into runtime manifests.
- Implemented logic to pull images based on defined pull policies.
- Enhanced validation for image metadata in package manifests.
- Added tests to ensure correct handling of image references and pulling behavior.
…st fingerprint and enhancing image selection logic
- Updated documentation to reflect the new package layout under 'bin/.dockpipe/internal/' instead of '.dockpipe/internal/'.
- Modified code in various files to ensure paths point to the new directory structure for compiled packages, workflows, and internal state.
- Adjusted tests to verify that the new directory structure is correctly utilized in the application.
jamie-steele and others added 30 commits July 11, 2026 18:15
Emit operation results for workflow validate and release upload
::inbox-item{title="TASK-002 commit prepared" summary="Use the focused prompt-brief commit message after staging four owned files"}
Security Hardening and Iterating on Orchestration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants