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

updog: Set permissions and extension of migrations #567

Merged
merged 1 commit into from
Nov 25, 2019
Merged

Conversation

sam-aws
Copy link
Contributor

@sam-aws sam-aws commented Nov 25, 2019

Issue #, if available:
Fixes #558

Description of changes:
When downloading migrations don't include the '.lz4' extension in the resulting file, and make sure the file is executable.

Signed-off-by: Samuel Mendoza-Jonas [email protected]

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Tested by checking the migration binaries after an update, before rebooting:

bash-5.0# updog check-update
aws-k8s-0.2.0 (v0.1)
bash-5.0# updog update-image
Starting update to 0.2.0
Update applied: aws-k8s-0.2.0
bash-5.0# ls -l /var/lib/thar/datastore/migrations/
total 1048
-rwxr-xr-x 1 root root 555720 Nov 25 21:30 borkseed-migration
-rwxr-xr-x 1 root root 514760 Nov 25 21:30 host-containers-version-migration
bash-5.0# /var/lib/thar/datastore/migrations/borkseed-migration
Usage: /var/lib/thar/datastore/migrations/borkseed-migration
            --datastore-path PATH
            ( --forward | --backward )

@sam-aws sam-aws merged commit f4d7b26 into develop Nov 25, 2019
@sam-aws sam-aws deleted the migration-names branch November 25, 2019 23:42
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.

[updog] Migration snafu's (unable to run migrations)
4 participants