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

Support set integration name for kamel run #40

Closed
lburgazzoli opened this issue Sep 11, 2018 · 4 comments · Fixed by #48
Closed

Support set integration name for kamel run #40

lburgazzoli opened this issue Sep 11, 2018 · 4 comments · Fixed by #48
Assignees
Labels
good first issue Does not require full understanding of the codebase kind/feature New feature or request

Comments

@lburgazzoli
Copy link
Contributor

the kamel run command determine the integration name using the integration file name but it would be nice to let the user set the name of the integration with an additional flag.

@lburgazzoli
Copy link
Contributor Author

@oscerd do you mind having a look ?

@nicolaferraro
Copy link
Member

I'll add also that the current mapping is trivial, e.g. MyIntegration.java -> myintegration.

A better name would be my-integration.

We should also make sure to respect Kubernetes conventions.

@lburgazzoli
Copy link
Contributor Author

lburgazzoli commented Sep 11, 2018

Thre is also a problem when the file is located on a different directory than the current one i.e. runtime/examples/Sample.java becomes runtimeexamplessample

@nicolaferraro nicolaferraro added good first issue Does not require full understanding of the codebase kind/feature New feature or request labels Sep 11, 2018
@oscerd
Copy link
Contributor

oscerd commented Sep 12, 2018

Sure

@oscerd oscerd self-assigned this Sep 12, 2018
squakez referenced this issue in squakez/camel-k Jun 21, 2021
* doc: new configuration explained

Ref apache#2003

* fix(doc): kube-config global flag

* doc(examples): http

* doc(examples): databases

* chore(examples): fix with resource dir
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Does not require full understanding of the codebase kind/feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants