Skip to content
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

[Spanner Backup & Restore] Provide ability to run Dataflow in another project to prevent accidental writing on-top of Spanner #12

Open
EricBeach opened this issue Mar 22, 2018 · 2 comments
Labels
SpannerBackupAndRestore issues related to the spanner backup and restore tool

Comments

@EricBeach
Copy link
Contributor

Enable the Dataflow job performing the backup or restore to run in a different project than the Spaner database. This would allow more detailed ACLs and reduce risk of a data corruption issue.

@EricBeach EricBeach changed the title Provide ability to run Dataflow in another project to prevent accidental writing on-top of Spanner [Spanner Backup & Restore] Provide ability to run Dataflow in another project to prevent accidental writing on-top of Spanner Nov 3, 2018
@nagarkar nagarkar added the SpannerBackupAndRestore issues related to the spanner backup and restore tool label Jan 25, 2019
@nagarkar
Copy link
Collaborator

Eric, can be done by external contributors (label it with 'help wanted' or 'good first issue' if appropriate?)

@EricBeach
Copy link
Contributor Author

Yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SpannerBackupAndRestore issues related to the spanner backup and restore tool
Projects
None yet
Development

No branches or pull requests

2 participants