Enable status subresource for integration

[astefanutti]

No description provided.

[nicolaferraro]

That's great!
I've made sure that the operator code doesn't touch the spec field, but only the status, but it may be subject to error if we don't enforce this rule.

Don't you need additional roles for changing the status?
E.g. look at here: https://github.com/knative/eventing-sources/blob/518626c9b16f6ad45aef00577fbcf3e249e1a584/config/rbac/rbac_role.yaml#L122

My expectation was that roles were not inherited by subresource.

[astefanutti]

That's great!
I've made sure that the operator code doesn't touch the spec field, but only the status, but it may be subject to error if we don't enforce this rule.

I've spent an hour reviewing the entire code to make sure the spec field wasn't updated to realize you had done an amazing job ;)!

Don't you need additional roles for changing the status?
E.g. look at here: https://github.com/knative/eventing-sources/blob/518626c9b16f6ad45aef00577fbcf3e249e1a584/config/rbac/rbac_role.yaml#L122

My expectation was that roles were not inherited by subresource.

Ah very good point. Let me add these additional roles...

[astefanutti]

After a second look at it, the current role definition is enough, as it uses wildcard for all camel.apache.org resources.

[nicolaferraro]

Right, that's why it's not needed here..