Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is Proof of Concept to make discussion easier. Why it happened:
* * * * *
and then deletes everything - claim, backups, namespace etc. we end up in state where we receive bill fot services but we're unable to match it with actual customer. We just receive info from Cloudscale that there are billing records for bucked named XXX owned by non existing UserID "some_long_id"How it's supposed to work:
If You want to delete, I must ensure it's completely billed otherwise I block deletion
It's still going to pop up in our logfiles, which I'm fine with, as long as we make sure there's an accounting record in the database.