Internal Fetcher runs even when k8s profile is set about catwatch

[jbellmann]

I will have a look next week.

[duergner]

@linki @jbellmann I did a minimal test and my conclusion would be that @Profile({"!test", "!k8s}) means that the component will be registered if not both profiles are active. That matches my understanding of the docu as well:

If a given profile is prefixed with the NOT operator (!), the annotated component will be registered if the profile is not active; for example, given @Profile({"p1", "!p2"}), registration will occur if profile 'p1' is active or if profile 'p2' is not active.

[duergner]

@jbellmann could you already have a look at this? Could someone else support you there?

[linki]

@duergner I'm curious about the or in the docs above. Does setting @Profile({"!test", "!k8s}) translate to?

given @Profile({"!test", "!k8s"}), registration will occur if profile 'test' is not active or if profile 'k8s' is not active.

Because this would mean it's activated whenever we don't run with the test profile, regardless of whether we're using the k8s profile or not.

[duergner]

That's my interpretation which also matches my observations from doing some testing with a minimal Spring Boot application.