The following self-signed certificate is issued for `consoleAdmin`. So, MinIO would associate it with the pre-defined `consoleAdmin` policy.

```
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            35:ac:60:46:ad:8d:de:18:dc:0b:f6:98:14:ee:89:e8

            }
            break;
        default:
            break;
        }
        return OptionalEntity.empty();
    }

    /**
     * Get the bad word.
     * @param form The create form.
     * @return The bad word.
     */
    public static OptionalEntity<BadWord> getBadWord(final CreateForm form) {
        final SystemHelper systemHelper = ComponentUtil.getSystemHelper();

 *       continuing to run {@code FooTest} itself. This is exactly what happens with {@code
 *       AndroidIncompatible}. But I'm not sure what would happen if we annotated the {@code
 *       suite()} method with {@code Suppress}. Would {@code FooTest} itself be suppressed, too?
 *   <li>In at least one case, a use of {@code sun.misc.FpUtils}, the test will not even

      description: "Is the goal of this change a performance improvement? If so, what quantifiable improvement should we expect? How would we measure it?"
    validations:
      required: false

  - type: textarea
    id: learning-curve
    attributes:
      label: "Would this change make Go easier or harder to learn, and why?"

  - type: textarea
    id: cost-description
    attributes:

 * <li>{@link #addBadWord(String, boolean)} - Add a bad word and optionally apply it.
 * <li>{@link #deleteBadWord(String)} - Delete a bad word.
 * <li>{@link #addElevateWord(ElevateWord, boolean)} - Add an elevate word and optionally apply it.
 * <li>{@link #deleteElevateWord(String, boolean)} - Delete an elevate word and optionally apply it.

```
.
├── app
│   ├── __init__.py
│   ├── main.py
│   └── test_main.py
```

The file `main.py` would have:

{* ../../docs_src/async_tests/main.py *}

The file `test_main.py` would have the tests for `main.py`, it could look like this now:

{* ../../docs_src/async_tests/test_main.py *}

## Run it { #run-it }

You can run your tests as usual via:

### High availability

A stand-alone MinIO server would go down if the server hosting the drives goes offline. In contrast, a distributed MinIO setup with _m_ servers and _n_ drives will have your data safe as long as _m/2_ servers or _m*n_/2 or more drives are online.

* `upgrade`: Upgrades

* **`200 - 299`** are for "Successful" responses. These are the ones you would use the most.
    * `200` is the default status code, which means everything was "OK".
    * Another example would be `201`, "Created". It is commonly used after creating a new record in the database.

                        .status(ApiResult.Status.OK)
                        .result());
    }

    /**
     * Retrieves a specific bad word setting by ID.
     *
     * @param id the ID of the bad word to retrieve
     * @return JSON response containing the bad word configuration
     */
    // GET /api/admin/badword/{id}
    @Execute
    public JsonResponse<ApiResult> get$setting(final String id) {