### Dataset Anonymization

In situations where importing a production dataset is unavoidable to reproduce an incident, legal guidelines strongly recommend anonymizing all the data involved.

To facilitate this, you can run one of the following commands from within your Docker container:

```bash
$ docker compose exec -it [container_name_or_id] php src/cron/anonymizeData.php licenceNumber anonymizeData env
```

**OR**

```bash
$ make anonymize_data LICENCE=licenceNumber ANONYMIZE=true|false ENV=env
```

#### Parameters:
- **`licenceNumber`**: The specific license number to anonymize. Input "all" to update all the licenses hosted on the server.
- **`anonymizeData`** (optional): Set this parameter to `true` to anonymize the data, and `false` to maintain the original data (default setting).
- **`env`** (optional): Designate the environment (options include qa, preprod, uat, local) to alter URLs accordingly. If the domain is not null, the default setting is `local`.

**Warning**: This command is executed from within the Docker container. Ensure to replace `[container_name_or_id]` with your actual Docker container name or ID.

#### Note:
- The command does not import or clone the license; it directly anonymizes the data in the specified license.

By adhering to this procedure, you maintain legal compliance while effectively addressing the incident through the reproduction of the dataset in a secure manner.