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: Do not filter Camel catalogs by runtime provider label #1900

Merged
merged 1 commit into from Jan 13, 2021
Merged

fix: Do not filter Camel catalogs by runtime provider label #1900

merged 1 commit into from Jan 13, 2021

Conversation

astefanutti
Copy link
Member

Fixes #1897.

This PR is intentionally minimal, to limit impacts of back porting it into the 1.3.x branch.

I'll create a follow-up PR to remove all the runtime provider related bits if no one objects.

Release Note

fix: Do not filter Camel catalogs by runtime provider label

@astefanutti astefanutti merged commit 045149f into apache:master Jan 13, 2021
@astefanutti astefanutti deleted the pr-152 branch January 13, 2021 15:39
@nicolaferraro nicolaferraro mentioned this pull request Feb 1, 2021
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.

Default catalog is ignored and the operator creates a duplicate
2 participants