Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(#4776): Fix catalog loading in camel trait #5086

Merged
merged 1 commit into from
Jan 22, 2024

Conversation

christophd
Copy link
Contributor

  • When new runtime version is used on integration the camel trait creates the catalog if it does not exist already
  • Use proper catalog namespace to verify that the catalog resource has been created during the camel trait execution

Fixes #4776

Release Note

NONE

- When new runtime version is used on integration the camel trait creates the catalog if it does not exist already
- Use proper catalog namespace to verify that the catalog resource has been created during the camel trait execution
Copy link
Contributor

@squakez squakez left a comment

Choose a reason for hiding this comment

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

Definetely! Better to make these things explicit! If you can add a unit test for this it would be even better :)

pkg/trait/camel.go Show resolved Hide resolved
@christophd christophd merged commit 2916247 into apache:main Jan 22, 2024
15 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.

1st Integration after Camel K runtime version update failing
3 participants