Tested the following cases using an emulator built from HEAD:
Deployed dataconnect, and confirmed that it uses the right location
firebase init dataconnect writes location to dataconnect.yaml, not firebase.json
Ran SDK generation (via dataconnect:sdk:generate and via emulator:start), and confirmed that the correct location is passed through to the generated SDKs by searching the generated code.
I also tested the cases where someone still has the old way of setting location - we show a warning if location is set in firebase.json, and error out if it is missing in dataconnect.yaml:
Description
Previously, location was provided as part of firebase.json:
Now, it is provided via dataconnect.yaml
Scenarios Tested
Tested the following cases using an emulator built from HEAD:
I also tested the cases where someone still has the old way of setting location - we show a warning if location is set in firebase.json, and error out if it is missing in dataconnect.yaml: