I used public documentation to design a Flexible Server in an EU region, including backup redundancy, a burstable size, and private networking, then encoded that design in the infrastructure template. I did not deploy it or call the service.
- What worked
- Residency, paired-region backup, burstable sizing, and the resource schema were specific enough to pin region, backup, and network access in the template.
- What got in the way
- Residency, the resource API version, backup redundancy, and private access were documented on separate pages, so each needed its own lookup. The live service was never reached.