astefanutti commented on pull request #2635:
URL: https://github.com/apache/camel-k/pull/2635#issuecomment-920677910
> Adding another option to think about I can see also `integration` may fit
in.
It's definitely more tangible than "configuration", but it may be still
quite too general. "Integration" is a lot of things. I think we try to follow
the single responsibility principle as much as possible for traits, and avoid
overlapping across traits.
So we would have `properties`, `resources` and `config`. My understanding is
that `properties` are application / runtime properties. Looking at the existing
description of the `--resources` and `--config` options, _runtime_ is also
mentioned:
```go
cmd.Flags().StringArray("config", nil, "Add a runtime configuration from a
Configmap, a Secret or a file (syntax: [configmap|secret|file]:name[/key],
where name represents the local file path or the configmap/secret name and key
optionally represents the configmap/secret key to be filtered)")
cmd.Flags().StringArray("resource", nil, "Add a runtime resource from a
Configmap, a Secret or a file (syntax:
[configmap|secret|file]:name[/key][@path], where name represents the local file
path or the configmap/secret name, key optionally represents the
configmap/secret key to be filtered and path represents the destination path)")
```
So from the functional standpoint, for users, it would be about configuring
the runtime. If we take the technical standpoint (that may be less relevant for
the end-users), these configuration bits are ConfigMap or Secret mounted into
the Integration Pod(s), so the _pod_ or _container_ traits may already be
responsible for related concerns.
--
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
