Announcements
The Google Cloud Community will be in read-only from July 16 - July 22 as we migrate to a new platform; refer to this community post for more details.
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

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

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 ?

0 2 212
2 REPLIES 2