Change Details

Once the Image Suggestions API is productionized, GrowthExperiments needs to be adjusted to use the new API. If the API signature doesn't change, all that's needed is to update `$wgGEImageRecommendationServiceUrl` / `$wgGEImageRecommendationServiceHttpProxy`. If it does change, we probably want separate classes for the old and new API so we can switch back and forth via configuration. Blocked by {T304891}. Blocks {T294362}.

Once the Image Suggestions API is productionized, GrowthExperiments needs to be adjusted to use the new API. ~~If the API signature doesn't change, all that's needed is to update `$wgGEImageRecommendationServiceUrl` / `$wgGEImageRecommendationServiceHttpProxy`. If it does change,~~ we probably want separate classes for the old and new API so we can switch back and forth via configuration. Example request: `curl https://image-suggestion.discovery.wmnet:30443/public/image_suggestions/suggestions/cswiki/344465` Example response: {P29341} Same request with the old API: {P29342} Blocked by {T304891}. Blocks {T294362}.

Once the Image Suggestions API is productionized, GrowthExperiments needs to be adjusted to use the new API. ~~If the API signature doesn't change, all that's needed is to update `$wgGEImageRecommendationServiceUrl` / `$wgGEImageRecommendationServiceHttpProxy`. If it does change,~~ we probably want separate classes for the old and new API so we can switch back and forth via configuration. Example request: `curl https://image-suggestion.discovery.wmnet:30443/public/image_suggestions/suggestions/cswiki/344465` Example response: {P29341} Same request with the old API: {P29342} Blocked by {T304891}. Blocks {T294362}.