nicolaferraro commented on issue #2080:
URL: https://github.com/apache/camel-k/issues/2080#issuecomment-788746088
> do we need the contentEncoding & contentMediaType ? as it is a resource,
we know that is should be either a binary config map or a secret so I guess the
encoding can be implicit.
>
I know it, but the "resource" is "x-camel" specific metadata, while the
Kamelet is supposed to tell an user (or a configuration UI) how to build a
valid configuration object, without mentioning configmaps or secrets, which are
Kubernetes concepts.
> With #2003, then will be multiple options to load from a location:
>
> * using an env var, like:
`google-storage://myCamelBucket?serviceAccountKey={{env:CAMEL_K_RESOURCES:DIR}}/secretName/token`
> * looking up from the classpath
`google-storage://myCamelBucket?serviceAccountKey=/secretName/token` (the
resources location should be part of the classpath, may not work on native)
> * extending the ResourceHelper to support serarching on pre-defined
locations (so it would be runtime dependant)
The problem is that a Kamelet can be used multiple times in an integration,
and so you might have multiple files with a location that is different on each
instance of the template. We need something instance-specific on top of the
features above...
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
