Releases: ploigos/ploigos-step-runner
Releases · ploigos/ploigos-step-runner
v0.15.0
purpose
- introduce StepResult and WorkflowResult
- refactor all StepImplementers to use StepResult
- refactor all the StepImplementer implementations unit tests for the StepResult refactor, and geneally make them more awesome
- narrow down initial API for v1.0.0
breaking changes
- ummm....yes
- quite a few StepImplementer config parameter names changed
- biggest break is in deploy (ArgoCD) moving from using a jinja templated values file to using
yq
to update values file in config repo
v0.14.0
Purpose
Intermediate step to v1.0.0 release in the github.com/ploigos org.
refactored / moved the following
- rhtconsulting/tssc-containers -> ploigos/ploigos-containers
- rhtconsulting/tssc-jenkins-library -> ploigos/ploigos-jenkins-library
added:
- ploigos/ploigos-charts
breaking changes
- create_container_image/buildah -
tlsverify
param changed totls-verify
Enhancements
- deploy/argocd - update to work with charts in a sub directory
Bug Fixes
- various cleanup
- sign_container_image/curl_push - update to work with Nexus and Artifactory
v0.13.0
v0.12.0
- Improved maven step implementer support for multiple servers
- Fixed an issue where ArgoCD step implementer sometimes created namespace names longer than the k8s character limit
- Improved error messages for failure scenarios in the config-lint and tag-source step implementers
v0.11.0
- Changed default branch from master to main
- Refactor openscap step to not require privileged container
- Refactor buildah step to not require privileged container
- Fixed an issue in the tag step where if url not provided and CI tool checks out source using username and tssc config provides a username/pass then everything breaks
- use a settings.xml for all maven steps to allow for disconnected.
- Added a utility function for logging into authenticated container registry
- buildah - update to use container registry login utility
- skopeo - update to use container registry login utility
- Fixed an issue where the LENGTH obfuscated data could be leaked
- clean up init imports to prevent circular imports