lburgazzoli commented on PR #5233: URL: https://github.com/apache/camel-k/pull/5233#issuecomment-1985320919
> > so I'm a little bit confusing about what is the `.status.conditions` we are talking about here :) > > NP. Let me try to summarize in shorter terms. `.status.conditions` already exists and it is meant to provide some info about possible info/warnings the user needs to know. Sometime ago I introduced another field, `.status.traits` whose goal was to store the executed traits in order to make the operator logic more consistent. However, this development was made based on the wrong assumptions provided in this PR description. The aim of this PR is to remove `.status.traits` which is inconsistent. Any user interested in troubleshooting an Integration can still rely on `.status.conditions` as it was doing previously. ok then, I was a little bit confused because the `.status.traits` has been the center of a number of things recently, like checksum, copy to kit, etc so I missed a little bit the context. sorry for the noise -- 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]
