squakez opened a new pull request #2771: URL: https://github.com/apache/camel-k/pull/2771
With this draft PR I've run some experiment to check how we can remove the `ResourceSpec` from the `IntegrationSpec` and still be able to let the user provide a local file as a resource. The idea is that the CLI will take care to parse a file, autogenerate to a `Configmap` and bind it to the `Integration` as it would be any other configmap. The resource will be owned by the Integration, so, deleted as soon as the Integration will be deleted. We also watch for resource file change to allow `--sync` option and regenerate the configmap upon a file change detection. With this approach (source code to be polished more) we can still keep the possibility for the user to provide a file and at the same time we can remove the need to include the resource content in the `Integration`. If we like this approach we can extend it to the `--openapi` and definetely remove the `ResourceSpec`. Ref #2320 <!-- Description --> <!-- Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". If no release note is required, write "NONE". You can (optionally) mark this PR with labels "kind/bug" or "kind/feature" to make sure the text is added to the right section of the release notes. --> **Release Note** ```release-note NONE ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
