Problem Statement

On several occasions we neglect running helm test. We only run it if deployments are changed, but in reality, other things can affect the end result, such es kubebuilder annotations or changes to the API. In those cases we ignore the test runs and that's just bad.

Also, we neglect to run helm.test.update to make sure that changes are reflected in the helm test. So now, check-diff is running helm.test.update and test.crds.update to see if there are any changes that need to be pushed into the helm tests.

Related Issue

Fixes #...

Proposed Changes

How do you like to solve the issue and why?

Format

Please ensure that your PR follows the following format for the title:

feat(scope): add new feature
fix(scope): fix bug
docs(scope): update documentation
chore(scope): update build tool or dependencies
ref(scope): refactor code
clean(scope): provider cleanup
test(scope): add tests
perf(scope): improve performance
desig(scope): improve design

Where scope is optionally one of:

• charts
• release
• testing
• security
• templating

Checklist

• I have read the contribution guidelines
• All commits are signed with git commit --signoff
• My changes have reasonable test coverage
• All tests pass with make test
• I ensured my PR is ready for review with make reviewable