Open
Conversation
CH-166 fix syntax issue
CH-170 fix secrets upgrade
Release/3.0.0
- Updated deployment configurations to include optional helm metadata arguments such as chart name, chart version, and app version in `codefresh-template-stage.yaml` and `codefresh-template-test.yaml`. - Refactored helm chart creation logic to support these new parameters in `helm.py`. - Added new field `image_name` in ApplicationHarnessConfig to allow custom image naming. - Updated OpenAPI and model documentation to reflect the new `image_name` field. - Added tests to validate the inclusion of helm metadata arguments and image name overrides in deployment configurations. - Cleaned up unused build steps in `codefresh-test.yaml` and removed redundant commands.
filippomc
commented
Feb 20, 2026
| commands: | ||
| - bash cloud-harness/install.sh | ||
| - harness-deployment $PATHS -d ${{DOMAIN}} -r ${{REGISTRY}} -rs '${{REGISTRY_SECRET}}' -n ${{NAMESPACE}} --write-env -e $ENV --cache-url '${{IMAGE_CACHE_URL}}' $PARAMS | ||
| - export HELM_META_ARGS="$( [ -n "${{HARNESS_CHART_NAME}}" ] && printf -- "--name %s " "${{HARNESS_CHART_NAME}}"; [ -n "${{HARNESS_CHART_VERSION}}" ] && printf -- "--chart-version %s " "${{HARNESS_CHART_VERSION}}"; [ -n "${{HARNESS_APP_VERSION}}" ] && printf -- "--app-version %s" "${{HARNESS_APP_VERSION}}" )" |
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request improves the distribution of Helm charts by adding customization options for image names and chart metadata. The changes support custom image names for applications, allow overriding Helm chart metadata (name, version, appVersion), and add conditional publishing controls for CI/CD pipelines.
Changes:
- Added
harness.image_namefield to allow applications to use custom Docker image names instead of directory-based names - Added CLI arguments (
--name,--chart-version,--app-version) to customize Helm chart metadata during deployment - Added publish skip conditions for Codefresh CI/CD to enable selective image publishing
- Added upgrade documentation for migrating from CloudHarness 2.x to 3.x
- Added GitHub Copilot instruction files for better AI assistant integration
- Version change in models library from 3.0.0 to 1.0.0
Reviewed changes
Copilot reviewed 26 out of 26 changed files in this pull request and generated 11 comments.
Show a summary per file
| File | Description |
|---|---|
| tools/deployment-cli-tools/ch_cli_tools/helm.py | Implements custom image name support and chart metadata merging logic |
| tools/deployment-cli-tools/ch_cli_tools/codefresh.py | Adds publish skip condition logic for controlling image publishing |
| tools/deployment-cli-tools/ch_cli_tools/utils.py | Adds null check to get_image_name function |
| tools/deployment-cli-tools/harness-deployment | Adds CLI arguments for chart metadata customization |
| tools/deployment-cli-tools/tests/test_helm.py | Adds tests for image name override and chart metadata features |
| tools/deployment-cli-tools/tests/test_codefresh.py | Adds tests for publish skip conditions and helm metadata args |
| tools/deployment-cli-tools/tests/test_skaffold.py | Updates tests to use dynamic image names from values |
| tools/deployment-cli-tools/tests/resources/applications/myapp/deploy/values-imagename.yaml | Test fixture for custom image name feature |
| libraries/models/pyproject.toml | Changes version from 3.0.0 to 1.0.0 (potential issue) |
| libraries/models/cloudharness_model/models/application_harness_config.py | Adds image_name field to ApplicationHarnessConfig model |
| libraries/models/api/openapi.yaml | Adds image_name field to API schema |
| libraries/models/docs/ApplicationHarnessConfig.md | Documents the new image_name field |
| docs/model/ApplicationHarnessConfig.md | Documents the new image_name field |
| docs/upgrades/2.x_3.x.md | New upgrade documentation for migrating from 2.x to 3.x |
| deployment-configuration/codefresh-template-*.yaml | Adds HELM_META_ARGS environment variable construction |
| deployment/codefresh-test.yaml | Generated file with updated build order and helm metadata args |
| applications/samples/deploy/values.yaml | Example usage of custom image_name and cloudharness-base dependency |
| .github/instructions/*.md | New GitHub Copilot instruction files for project guidance |
| openapitools.json | Deleted OpenAPI generator configuration |
| ch-166.patch | Deleted patch file |
| deployment-configuration/codefresh-template-stage-onpremise.yaml | Deleted on-premise deployment template |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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
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.
Closes CH-239
Implemented solution
Generation scripts and templates have been changed to include the new parameters and configuration
How to test this PR
Check the test deployment:
Sanity checks:
Breaking changes (select one):
breaking-changeand the migration procedure is well described abovePossible deployment updates issues (select one):
alert:deploymentTest coverage (select one):
Documentation (select one):