You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have the (regulatory and business/security) requirement to store additional "build information" with the resulting (docker) image.
Easiest way from our perspective would be to have the option to add additional labels for the resulting (docker) image.
Thus it would be great if there would be a way to pass this information when e.g. running "kamel run"
The text was updated successfully, but these errors were encountered:
I think we could add some feature to influence the IntegrationKit build (maybe the builder trait?). However, the presence of customizable labels may limit the possibility of kit reuse among Integrations, requiring a new build everytime. That would be a tradeoff to consider. In any case, any contribution is welcome as usual.
In the while, a possible workaround if you have a fixed list of labels is to create a base image from the openjdk one with that list of labels and using this one as base image for the Integrations.
This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!
We have the (regulatory and business/security) requirement to store additional "build information" with the resulting (docker) image.
Easiest way from our perspective would be to have the option to add additional labels for the resulting (docker) image.
Thus it would be great if there would be a way to pass this information when e.g. running "kamel run"
The text was updated successfully, but these errors were encountered: