GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
# To generate all operators you have to run the script repeatedly, each time with a different toml file.
```
## Intended development workflow
Adding a new operator is as easy as adjusting one of the existing `operators-<operator-group>.toml` files, or adding a new one.
If you want to update the generator, make the necessary changes in the `generate` directory.
It is a good idea to test your changes locally.
In your commit, do not include changes to the `operators` directory.
After pushing your changes to the remote, our CI automatically regenerates all operators from all `operators-<operator-group>.toml` files present in the repository.
In this process, any changes you made under `operators` will be lost.
After the pipeline has passed, you can trigger the manual job `file-mr` to create a new merge request including your changes and the freshly generated operators.
Using the CI makes sure that the generated code is always in sync with the description of what and how to generate.
