gitlab

Your mission

Return whether a path is safe to wipe: it must sit inside the backup root, not out in production.

today's brief

January 31, 2017. A tired GitLab engineer fighting a spam wave at 11pm runs a delete to clear a broken database directory, then watches in horror as it chews through the primary instead of the empty secondary. 300 GB of live production data gone in seconds, and five separate backup methods turn out to be broken. The guard that would have saved them: only ever delete inside the backup root, nowhere else.

See it in action

under_backup_root("/var/opt/backup/db-2017")

Expected result

Your checklist

For your own tracking. Tests grade your code.

The only safe place to delete is under /var/opt/backup/.
Return 1 if path begins with /var/opt/backup/ and has at least one more character after that prefix.
Return 0 for anything else, including the prefix on its own or any production path.

More examples

under_backup_root("/var/opt/gitlab/data")

Expected result

under_backup_root("/var/opt/backup/")

Expected result

Constraints

Expected files

backup.c

Allowed functions

None. Write every helper yourself.

Back to compete

Solutions

gitlab

Your mission

Return whether a path is safe to wipe: it must sit inside the backup root, not out in production.

today's brief

See it in action

under_backup_root("/var/opt/backup/db-2017")

Expected result

Your checklist

For your own tracking. Tests grade your code.

The only safe place to delete is under /var/opt/backup/.
Return 1 if path begins with /var/opt/backup/ and has at least one more character after that prefix.
Return 0 for anything else, including the prefix on its own or any production path.

More examples

under_backup_root("/var/opt/gitlab/data")

Expected result

under_backup_root("/var/opt/backup/")

Expected result

Constraints

Expected files

backup.c

Allowed functions

None. Write every helper yourself.

Back to compete

Solutions