added the results to the document

Reproduced the above steps on production then tried the user's query and it all worked with some results.
Next step is for us to investigate why this happened.

We tested that the same query fails on staging.
We ran the allowlist job with kubectl exec -it deployment/api-queue-default -- sh -c "php artisan job:dispatchNow UpdateQueryserviceAllowList" on staging and can confirm that the allowlist.txt: key of the queryservice-allowlist configmap is now populated.
We restarted the query service with k rollout restart deployment/queryservice.
Then we confirmed that federated query now works on staging.

Given that the dependabot changes are all github actions version upgrade, i did not expect the merge to have some impact on the app. That said after the deploy to staging I logged into a wiki on wikibase.dev and access the queryservice tool. it looked healthy and was working so I will deploy this on production and do the same check.

https://github.com/wbstack/ui/pull/1117

EOD update: I put up a daft PR with what I have so far. currently the PR causes 2 tests to error. The next thing will be to fix the cause of those errors and remove trailing spaces and unwanted comments. I also plan on adding a data provider in the validator test so that I can pass a biggest number of invalid and valid test data.

Opening this ticket and picking it as T419210 and T419221 are done

This was the only found place https://github.com/wmde/wbaas-deploy/blob/main/bin/local/create-local-wiki.sh . I used grep to search through the repos for /wiki/create and also searched for the use of the payloads sitename|profile to find anyplace that will need the KER added.

@Anton.Kokh nothing found. I added the output from the script in the file given above

I tested this on production . by creating an item and adding a mul label https://newwiki.wikibase.cloud/wiki/Item:Q2

I tested this on staging. by creating an item and adding a mul label https://somewiki.wikibase.dev/wiki/Item:Q1.
then I did kubectl port-forward pod/elasticsearch-2-datapod 9999:9200 and curl 'http://localhost:9999/_search?pretty=true&q=boytchelibou'

opening this as T416178 has been moved to done

I checked and all the jobs have ran to completion. I did the check using

We tried running the ElasticsearchAliasInit job on fresh docker compose setup with docker compose exec api bash -c 'php artisan job:dispatchNow ElasticSearchAliasInit 1 elasticsearch'and we got no output but interestingly we tried it on minikube with the new elasticsearch cluster as kubectl exec deployments/api-scheduler -- bash -c "php artisan job:dispatchNow ElasticSearchAliasInit 1 elasticsearch-3:9200" such and had some output

I started work on this by cloning the dolly-20260213-c template on the vm started the minikube-tunnel and did the port fowarding to my machine with sudo ssh -i ~/.ssh/id_rsa -vNL 443:localhost:443 root@172.16.66.XX and I repeatedly hit this error on firefox
Secure Connection Failed An error occurred during a connection to wbaas.dev. PR_CONNECT_RESET_ERROR. I am suspecting it is again related to the ¨Fritzbox" issue but I also tried changing the wifi network by connecting to my mobile hotspot and that did not solve it. I also tried to edit the ssh config at /etc/ssh/sshd_config by setting AllowTcpfowarding to yes and ran sudo service ssh restartbut that did not fix it so i undid the config change as I expect it to work without having to do the ssh config tweking.

Indices created and mediawiki is now writing data to them so this can now be worked on.

Tested on Production. Made a new item with a very unique string. As above checked it was in elasticsearch-3 with curl. We cheched the google cloud console and we saw no erro related to this deployment to production but we noticed some complains about Elasticsearch health checks fails.
Startup probe failed: elasticsearch 03:04:30.62 INFO  ==> Checking Elasticsearch health https://console.cloud.google.com/errors/detail/CJnOtciylYOLeQ;locations=global?project=wikibase-cloud