Would be nice if it points to the wiki page where there will be more info about the service and the beta process.

The message should be sent as a warning for all the user endpoints of the API, using the ResponseMessages model that's returned in all the responses. See:

• https://gitlab.wikimedia.org/repos/cloud/toolforge/components-api/-/blob/main/components/models/api_models.py?ref_type=heads#L167
• https://gitlab.wikimedia.org/repos/cloud/toolforge/components-api/-/blob/main/components/api/tool_router.py?ref_type=heads

Some useful hints:

• To access the api directly from your lima-kilo, you can use https://127.0.0.1:30003/, for examaple, to get the api definition https://127.0.0.1:30003/openapi.json
• You can use restish within lima-kilo to do bare API requests, once you become tf-test, example (I had no tool config created, so the error is expected xd, see the shape of the response though), use <tab><tab> to autocomplete, helps enormously:

• you can use toolforge_deploy_mr.py components-api once you have the MR created to deploy in lima-kilo
• Remember that the unit tests/pre-commit also help making sure things did not get broken

The warning message should be formatted on toolforge_weld to fit this template, "Warning: [msg]".