Checks not executed in a namespace with just a proxy entity.

[andrew-pickin-epi]

Checked created in a namespace with only proxy entries don't run.

Expected Behavior

Checking a check in a namespace, with given proxy_entity_name should create a check and entity and execute the test on the given schedule.

Current Behavior

No proxy entity is create of events generated.
Even explicitly creating the proxy entity explicity does not generate events.

Possible Solution

None

Steps to Reproduce (for bugs)

sensuctl namespace create Test
sensuctl --namespace Test asset create sensu/sensu-aws-sns-handler \
    -u  https://assets.bonsai.sensu.io/b3d7751856b5b61b43c83c906df26724d2678ae2/sensu-aws-sns-handler_0.5.0_windows_amd64.tar.gz \
 --sha512 e175740512fa5d96f1e735c81f9746cd16374c8907aaa69504b68e52d0db71027a824c35f4af4c3be771e6f1f9b9273b1d3bea83161c940bb1fd599a6c65e3b0
sensuctl --namespace Test check create NotFound -c "ls -l /not/found" --handlers sensu/sensu-aws-sns-handler -p --round-robin --proxy-entity-name test-proxy --subscriptions entity:test-proxy -i 300

Context

I was trying to create a namespace to partition the checks run by a proxy.
Note there are true entities (hosts and proxies) within other namespaces that work as expected, however these are all allocated, and I beieve a host can not exist with two namespaces.
Specifically I'm trying segregate to test that enquiry the status of AWS Load Balancers, these checks work when proxied in Namespace with other application checks, but I want to separate there into a new namespace, so Infrastructure and Application checks are seen by different teams.

Your Environment

Sensu 6.11.0.
Standard docker image, running on Alma Linux EC2 in AWS

[agm650]

If I remember well you need a non proxy entity to execute the check inside the same namespace of your proxy check.
one way to solve this issue (which is probably not recommended) is to execute your check inside another namespace and then with a dedicated handler to create the event in the correct namespace. I remember I did something like that once.

I’ll try to check if I can remember how to do this :)

[andrew-pickin-epi]

If I remember well you need a non proxy entity to execute the check inside the same namespace of your proxy check.

That's what I assumed. In which case, can I change this to a feature, where this isn't required.