You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the Dataflow run (which is essentially running a Java program locally), selecting a login account will provide the login cred to the Dataflow program when no service account is provided. If the optional service account is provided, the service account will be used instead.
For the App Engine local run, we have a very similar UI. The user can select a login account and provide a service account. However, only passed to the dev appsever is the service account.
Will it be worth passing a login account in case the service account is missing? The answer may be "no", as we push people to use the service account workflow as much as possible.
Or, it could be the other way around: stop providing the login cred for Dataflow runs.
The text was updated successfully, but these errors were encountered:
For the Dataflow run (which is essentially running a Java program locally), selecting a login account will provide the login cred to the Dataflow program when no service account is provided. If the optional service account is provided, the service account will be used instead.
For the App Engine local run, we have a very similar UI. The user can select a login account and provide a service account. However, only passed to the dev appsever is the service account.
Will it be worth passing a login account in case the service account is missing? The answer may be "no", as we push people to use the service account workflow as much as possible.
Or, it could be the other way around: stop providing the login cred for Dataflow runs.
The text was updated successfully, but these errors were encountered: