| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| options, | ||
| schema: serviceInfo.schema, | ||
| validateOnly: true, | ||
| schemaValidation: serviceInfo.dataConnectYaml.schema.datasource.postgresql?.schemaValidation, |
There was a problem hiding this comment.
Quick sanity check - does this get broken by our move from datasource -> datasources? @fredzqm might know off the top of his head.
Sorry, something went wrong.
There was a problem hiding this comment.
Chatted offline -- based on go/fdc:multi-data-source it looks like the datasource field will still be supported, though we should also support datasources in #7589.
Sorry, something went wrong.
…e` and `deploy` (#7639) * Support handling schema validation options in `diff`. * Format. * Don't output second set of diffs if they're equal to the first. * Update dataconnect:sql:migrate * Fix my failed rebase lol * Finish handling schemaValidation mode in `dataconnect:sql:migrate`. * Fix setSchemaValidationMode. * Concat follow-up strict diffs, instead of replacing compat diffs. * Don't display purely optional changes with flag. * Pass `schemaValidation` into `deploy` command. * Address review comments.
| Back | FazBrowse Home | New Git URL |
Description
Updates firebase dataconnect:sql:migrate and firebase deploy per go/fdc-compat-mode-cli-api.
Scenarios Tested
schemaValidation unset, both required and optional changes:
schemaValidation unset, only required changes:
schemaValidation unset, only optional changes:
schemaValidation=COMPATIBLE, both required and optional changes:
schemaValidation=COMPATIBLE, only optional changes:
schemaValidation=STRICT, both required and optional changes:
Sample Commands
firebase deploy, with schemaValidation unset, both required and optional changes, and default options selected:
