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

chore(Canvas): Remove Route name restriction #1061

Closed
wants to merge 1 commit into from

Conversation

lordrip
Copy link
Member

@lordrip lordrip commented May 3, 2024

Context

Currently, the route name validator is too strict, whereas Camel JBang accepts route names as:

  • AnotherRoute
  • My Route
  • #$%^&$%^

This PR disable that validation section.
image

While keeping the unique ID validation
image

fix: #968

@lordrip lordrip force-pushed the chore/remove-name-restrictions branch from 1dd7bf2 to f370b59 Compare May 3, 2024 10:26
@lordrip lordrip requested a review from igarashitm May 3, 2024 12:35
@apupier
Copy link
Member

apupier commented May 3, 2024

Are all these patterns working too when deployed with Camel K? Based on previous rule of validation it smells like OpenShift resource id pattern restrictions

@lordrip
Copy link
Member Author

lordrip commented May 3, 2024

Are all these patterns working too when deployed with Camel K? Based on previous rule of validation it smells like OpenShift resource id pattern restrictions

I tried it also in the Developer Sandbox and it worked as well, using the CamelK extension, also the integration name it's the filename

@lordrip
Copy link
Member Author

lordrip commented May 3, 2024

Closing the PR for now, as we need to rework the validation part to apply partially depending on the entity

@lordrip lordrip closed this May 3, 2024
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.

too restrictive validation for new route id values
3 participants