How can we block traffic to a Message Processor in a specific environment ?

[adevegowda]

We have one of the MPs shared across 3 environments. We would like to remove the MP from two active environments (let's say env1, env2) and place into inactive environment (let's say env3) for testing.

So I ran the below command to deregister Message Processor from the organization's environments as per this link

curl -u adminEmail:pWord -X POST http://{management-ip}:8080/v1/o/{orgName}/e/{envName}/servers -d "uuid={uuid}&region={regionName}&pod={podName}&action=remove"

However, we observe that this Message Processor is still receiving the traffic in the two environments env1 and env2 for which the Message Processor has been deregistered.

Can you please let me know how can we ensure that the Message Processor doesn't receive the traffic in these two environments env1 and env2, but it continues to receive traffic in the environment env3 ?

[API-Evangelist]

Instructions provided in step 1 should resolve if you followed correctly.

Simple check will help.Run below command to verify what all mp's are associted.

curl -iu username localhost:8080/v1/o/{orgname}/e/{envname}/servers -X POST -d 'uuid={uuid} region={regionName}&pod={podName}&action=remove'

curl -v -iu username localhost:8080/v1/o/{orgname}/e/{envname}/servers

[#3]

Get Message Processors associated to environment:

curl -u <adminEmail> http://<ms_IP>:8080/v1/o/<org_name>/e/<env_name>/servers

Get Message Processor UUID:

curl -v http://<mp_IP>:8082/v1/servers/self/uuid

Remove Message Processor from Environment:

curl -v -u <adminEmail> -X POST http://<management-ip>:8080/v1/o/<orgName>/e/<envName>/servers 
-d "uuid=<uuid>&region=<regionName>&pod=<podName>&action=remove"

Add Message Processor to Environment:

curl -v -u <adminEmail> -H "Content-Type: application/x-www-form-urlencoded" 
-X POST http://<ms_IP>:8080/v1/o/<org_name>/e/<env_name>/servers" -d "action=add&uuid=<mp_UUID>