mrinalsharma commented on PR #592: URL: https://github.com/apache/camel-karavan/pull/592#issuecomment-1374957731
> 1. `karavan-secrets.yaml` might include username and password/token to access to the repository - Token is not something pre-configured, urer needs to have a Token created by running aws-cli tool. This token also has a short life. So users will have to continuously keep updating karavan-secrets.yaml. This will be a big nuisance to users. - If we make Container repository creation a pre-requisite step then again for each project user will have to go out of Karavan-app and create a repo. - **The operator is not creating a Repo, the operator is just creating a karavan-task-dev-quarkus, karavan-task-dev-spring, as part of this task execution, the repo is getting created.** . - Please suggest if you still want me to remove the task that creates the repo. Add a token to the secret? 2. Do you mean we don't need OPENSHIFT and Kubernetes keys and if AWS key is set then consider running in AWS env and use AWS properties? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
