tree 1f55653bbc25434641e40cd677dc59818cfb011f
parent 57eccf48e418e0243f586a945134785dbe9b5d08
author Zixuan Liu <nodeces@gmail.com> 1640691017 +0800
committer GitHub <noreply@github.com> 1640691017 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhyvVJCRBK7hj4Ov3rIwAAj0MIAGFX96eyv1yZbsRnuxE3lMrd
 i+VNV8/yxDp3LpYsQZR9rpkg75MsKk/FkVkPpwhKSI7rUpD3KqoNK83W3wUEYkWw
 Z3BlwFwD/NfltOFcT0v60cc1waOHREPpSTrDGnqMdsxPlaRIBgl8uphDLLDEvmWG
 P9L414nkQovKm3nAvBoE/MHIQrDpNnmJHyeCH0/Z/mef7JOorj5x9PaJG7oMOz2b
 hMvm9wKa8paAwTHGmp1sTR8aDeEEXidmE+poLzlxO5hUJ1R694OOCGz9t3y4Pwkn
 wACFOzSZweSLUj/K8R5keoLkf7YoKKt/a8YkF61cs0hz1n87k9nmBaeJhBualH0=
 =GGn4
 -----END PGP SIGNATURE-----
 

[Broker] Remove check resource when delete failure domain (#13421)

### Motivation

This PR is used to keep same behavior with Pulsar 2.8 and 2.7 version.

In Pulsar 2.7 and 2.8, when delete a non-existent failure domain resource, it will return 404 status code.
In Pulsar 2.9, when delete a non-existent failure domain resource, it will return 200 status code.

Reproduce in Pulsar 2.8:
```
$ docker run -itd \
  -p 6650:6650 \
  -p 8080:8080 \
  apachepulsar/pulsar:2.8.1 \
  bin/pulsar standalone
$ pulsarctl clusters delete-failure-domain standalone non-existent-failure-domain
[✖]  code: 404 reason: Domain-name non-existent-failure-domain or cluster standalone does not exist
```

Reproduce in Pulsar 2.9:
```
$ docker run -itd \
  -p 6650:6650 \
  -p 8080:8080 \
  apachepulsar/pulsar:2.9.0 \
  bin/pulsar standalone
$ pulsarctl clusters delete-failure-domain standalone non-existent-failure-domain
Delete failure domain [non-existent-failure-domain] for cluster [standalone] succeed
```
                   
Affected version: 2.9.x

This issue was caused by https://github.com/apache/pulsar/pull/11693.

### Modifications

- Remove check resource exists when call the `ClusterResources#deleteFailureDomain()`
- Add check resource exists when call the  `ClusterResources#deleteFailureDomains()`