Draft PR adding tests up at https://github.com/wbstack/api/pull/1105

Could well be that the classes referenced in config/horizon-exporter.php have now been renamed and that's all we need to fix

The queryservice was probably last restarted with a node pool update around April 6th. We expect the Platform API Laravel job that failed to properly create the ConfigMap ran between April 6th and April 14th.

Paused while we work on an incident

Shipped the reverts to production. Next up for this ticket is to:

• identify why this version bump didn't work
  • see if this missing class issue is reported on github
• determine if we could add a test that checks this path
• see if there is a version that would work

Thanks for the report. I can replicate this issue. I looked under the hood and and I can see that indeed the allowlist seems to be empty. I guess we have a bug in building it:

Had a reply from Wikibase Suite Team

we've discussed it and the best option for us would be adding the new "intended_for_reuse" boolean field and then we'll handle the filtering for UI

@dang mentioned he tested this in a local minikube cluster but is uncertain about how it will behave on staging so please pay particular attention to that

We now acknowledge that the relevance of this has drifted somewhat and our focus has shifted. We might find that by the time we get to implementation that T400456 or similar has made progress.

merged and tested to be a no-op on staging and production so far

Unstalled with the intention of getting at least a temporary fix for this user.
We'd be happier allowlisting a limited range of CORS so it would help to get the URL the user wants to embed our content into.
Also waiting to be added to some WMF slack channel to to talk about this

Part of this week's focus now

deployed to production. Did no more confirmation here. I believe it is sufficient to test on staging

deployed to staging. Confirmed that I can make a Wiki still whether or not I provide a KER

PR for the requested changes on our UI is up and should be merged and deployed tomorrow (April 2nd) pending approval.

Search performed and updated the file with the output of the search. No emails found.

Unfortunately at the very last minute, post deploying to staging, we realised this ticket is invalid.

We're now into Q2 and we've finished the delivery (if not the final clean-up) of T416907: 🦄CTKE: User creates a new permanent instance

We are waiting to have a chat with WMF.

After attending kubecon we discussed that might be interesting to estimate the effort of "per instance swagger" where we create a new deployment of swagger for each instance but we keep them mostly scaled to 0 using Kubernetes-based Event Driven Autoscaling - HTTP Add-on

Pushed a couple of changes and happy to be hands off again.

Discovered we want placeholder not label. Updated task description.

Taking this over from @Ollie.Shotton_WMDE for a moment

Just tested I could make a new wiki using the UI on production

Deployed on staging. Expedited the deployment and avoided waiting for argo with ./bin/argocli app sync api