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

Extract Redis tar more resilient #335

Merged
merged 1 commit into from
Aug 3, 2023
Merged

Extract Redis tar more resilient #335

merged 1 commit into from
Aug 3, 2023

Conversation

johha
Copy link
Contributor

@johha johha commented Aug 3, 2023

The root dir of the Redis tar file can have various names depending on where/ how it is downloaded:

-> All other files of the tar are identical as they are based on the same github release.

To avoid packaging errors during deploy time this change ensures that the extracted root dir of the tar file will be named 'redis-'. This will also prevent version conflicts.

  • I have viewed signed and have submitted the Contributor License Agreement

  • I have made this pull request to the develop branch

  • I have run CF Acceptance Tests on bosh lite

The root dir of the Redis tar file can have various names depending on
where/ how it is downloaded:
- When the tar is downloaded via the Concourse 'github-release-resource'
  the dir will be named 'redis-redis-<commit-hash>'.
- However when the tar is manually downloaded from the redis github
  release (e.g. https://github.com/redis/redis/archive/refs/tags/7.0.12.tar.gz)
  the dir will be named 'redis-<version-number>'

-> All other files of the tar are identical as they are based on the
same github release.

To avoid packaging errors during deploy time this change ensures
that the extracted root dir of the tar file will be named 'redis-<version-number>'.
This will also prevent version conflicts.
@johha johha merged commit e068ba3 into develop Aug 3, 2023
1 check passed
@johha johha deleted the redis-tar branch August 3, 2023 11:21
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.

3 participants