[07:54:10] isaranto: yeah, only the rate limits may slightly change, the "risk" is if I messed up some config, and we can revert pretty easily [07:55:17] thanks! just wanted to be clear although this is documented in https://api.wikimedia.org/wiki/Talk:Community#Announcement:_API_Portal_shutdown [07:56:07] claime: given that this change is transparent to the clients then we leave it up to you -- whatever is easier and makes things more convenient for you [07:56:17] thank you for all the work <3 [07:56:35] ok awesome, thanks :) [08:04:34] claime: I'll wait also for someone from our team to chime in in case I am missing something cc: klausman are there any risks or concerns we should raise to Claime? [08:23:11] claime: to clarify: would this be in addition to the APIGW functinality? or would the traffic be switched (at what level? I suspect you wouldn't switch the DNS names around?) [08:24:02] klausman: the migration happens at the ATS level. For clients nothing changes, for you traffic will come from the rest-gateway instead of the api-gateway [08:24:22] I see. I think we should be good to go, then [08:24:35] we're just consolidating [08:24:44] We'll have to update our docs re: api keys, of course [08:25:10] klausman: reach out to Alexandra Paskulin [08:31:08] ty!@ [12:08:01] in https://api.wikimedia.org/wiki/Talk:Community#Announcement:_API_Portal_shutdown it mentions that most API keys will continue to work. so yes we should clarify what most means [14:26:24] 10Lift-Wing, 06Machine-Learning-Team, 06ServiceOps new, 10ServiceOps-SharedInfra, and 5 others: Reroute LiftWing endpoints - https://phabricator.wikimedia.org/T422804#11833678 (10KartikMistry) @Clement_Goubert Hi, do we need to change anything on the recommendation-api side for this change?