Skip to content

Conversation

@yaelibarg
Copy link
Contributor

  • Introduced imageName field in values.yaml to allow users to specify a custom container image name.
  • Added a helper function to generate the default image name based on integration type and version.
  • Updated deployment templates to utilize the new imageName field, falling back to the default if not provided.

Type of change

Please leave one option from the following and delete the rest:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Non-breaking change (fix of existing functionality that will not change current behavior)
  • Documentation (added/updated documentation)

- Introduced `imageName` field in values.yaml to allow users to specify a custom container image name.
- Added a helper function to generate the default image name based on integration type and version.
- Updated deployment templates to utilize the new `imageName` field, falling back to the default if not provided.
Copy link
Contributor

@omby8888 omby8888 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

- Updated values.yaml to change `imageName` field to `image` for clarity.
- Modified helper function to reflect the new image naming convention.
- Adjusted deployment templates to use the updated `image` field, ensuring backward compatibility with default image generation.
- Introduced a new helper function to standardize the container image retrieval process.
- Updated deployment and cron job templates to utilize the new helper function for image definition, enhancing maintainability and clarity.
@yaelibarg yaelibarg merged commit f210ff2 into main Nov 18, 2025
3 checks passed
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