-
Notifications
You must be signed in to change notification settings - Fork 950
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support firebase dataconnect:sdk:generate --watch
#7719
Conversation
firebase dataconnect:sdk:generaate --watch
firebase dataconnect:sdk:generate --watch
@@ -8,9 +8,11 @@ import { load } from "../dataconnect/load"; | |||
import { readFirebaseJson } from "../dataconnect/fileUtils"; | |||
import { logger } from "../logger"; | |||
|
|||
type GenerateOptions = Options & { watch?: boolean }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Can be defered] [Not blocking PP, lower priority than compatible modes docs]
While we are at this. It would nice if sdk:generate
also takes optional [serviceId] [connectorId]
like other commands.
The rule of thumb from go/fdc:multi-data-source: if there are >1 services / connectors / datasource, it defaults to run the same routine against all relevant resources.
dataconnect:services:list list all deployed services in your Firebase
project
dataconnect:sql:diff [serviceId] displays the differences between a local
DataConnect schema and your CloudSQL database's
current schema
dataconnect:sql:migrate [options] [serviceId] migrates your CloudSQL database's schema to
match your local DataConnect schema
dataconnect:sql:grant [options] [serviceId] Grants the SQL role <role> to the provided user
or service account <email>.
dataconnect:sdk:generate generates typed SDKs for your Data Connect
connectors
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Filed b/369400626 to update all commands per go/fdc:multi-data-source, as I believe right now an error is thrown in diff/migrate/grant if serviceId isn't specified and multiple services exist.
Description
Scenarios Tested
Sample Commands