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

Add warnings about tronctl disable not being permanent #973

Merged
merged 1 commit into from
Jun 10, 2024

Conversation

nemacysts
Copy link
Member

As we learned in a recent incident, if there are any issues with the DynamoDB data, it's possible for us to end up re-enabling jobs. We've previously warned folks in the past (in Slack/IRC/etc) that to permanently disable jobs it's recommended that they do so in soaconfigs, but this is easy to forget and not everyone will reach out before disabling a job that they don't expect to re-enable any time soon.

As we learned in a recent incident, if there are any issues with the
DynamoDB data, it's possible for us to end up re-enabling jobs. We've
previously warned folks in the past (in Slack/IRC/etc) that to
permanently disable jobs it's recommended that they do so in soaconfigs,
but this is easy to forget and not everyone will reach out before
disabling a job that they don't expect to re-enable any time soon.
@nemacysts nemacysts merged commit 586a440 into master Jun 10, 2024
4 checks passed
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

Successfully merging this pull request may close these issues.

2 participants