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

do not automatically delete state-persisting instruments when they are removed from the bigband file #27

Open
imaman opened this issue Jun 20, 2019 · 0 comments

Comments

@imaman
Copy link
Owner

imaman commented Jun 20, 2019

auto-deletion of lambda functions is fine because you can easily rollback by means of source-control-reverting. However, for state-persisting instruments (dynamodb, s3) this is not the case. once auto-deleted was carried out, we cannot restore the data, and it is effectively lost.

we need to protect user from accidental deletion of state-persisting instruments. Two directions that come to mind:

  • a special command line flag to signal the user's explicit will to delete such instruments (probably the flag should explicitly list the names of the instruments to be deleted)
  • a special limbo zombie instrument to replace the actual instrument. when such a bigband is shipped deletion will occur. Otherwise, removal of a (non-zombie) state-persisting instrument will not result in an actual deletion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant