Adding to the wbstack test situation vs other test situation, the essential steps for having some sort of test site (without elastic) on wbstack would be:
- Make a new wbstack mediawiki 1.36 image, with latest of Wikibase (could be built nightly?)
- Setup the new DB Schemas for the new 1.36 system & hook them up to the platform
- Deploy a new service with the new mediawiki image (and thus federated properties)
- Manually deploy a site using the new service etc for testing fedey props
This would leave all wbstack sites in ye old situation, and just have 1 site that could be "continually deployed" to.
These steps would result in a test site that 1) doesnt have elastic, 2) OAuth for service such as quickstatements & cradle would continue to point at the old service 3) a small amount of aditional stuff might also be needed, like poking something to do with the query service.
IMO all of this would draw focus away from the focus of this hike, being feddy props, and thus might not be a good idea for this round to look at.
And if there were more unexpected things it would slow it down further etc
We would probably also want ElasticSearch to be installed per the requirements in the parent ticket.