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
The traits configuration is stored in the Integration, IntegrationKit and IntegrationPlatform resources. While this makes trait configuration part of the Camel K public API, it is not defined in any schema, and is loosely validated.
Following #1600, the traits structs are used directly for serialisation. Instead of declaring map[string]TraitSpec fields in the API, we could make the traits structs part of the Camel K API, and refer to them from the Integration, IntegrationKit and IntegrationPlatform types.
With #1582, the traits configuration schema will automatically be generated and included in the CRDs structural schemas.
The text was updated successfully, but these errors were encountered:
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!
The traits configuration is stored in the
Integration
,IntegrationKit
andIntegrationPlatform
resources. While this makes trait configuration part of the Camel K public API, it is not defined in any schema, and is loosely validated.Following #1600, the traits structs are used directly for serialisation. Instead of declaring
map[string]TraitSpec
fields in the API, we could make the traits structs part of the Camel K API, and refer to them from theIntegration
,IntegrationKit
andIntegrationPlatform
types.With #1582, the traits configuration schema will automatically be generated and included in the CRDs structural schemas.
The text was updated successfully, but these errors were encountered: