Chronicle API Migration Legacy Endpoints

There’s a variety of endpoints listed in the Chronicle API documentation that still have “legacy” in the name. ​@SoarAndy in a post about five months mentioned that this just reflects the API call not being the Google structure yet. However, I am concerned that these endpoints are only usable using the v1alpha version, which Google documentation warns is not suitable for production as it could be changed unpredictably. With the migration deadline so close, I am concerned about being forced to switch existing use cases to use these unstable endpoints while knowing I have no choice.

Does the use of the v1alpha with these legacy endpoints truly mean that they are unstable and not fit for production?