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

Remove old cached bundle on refresh #993

Merged
merged 1 commit into from
Apr 16, 2020

Conversation

carolynvs
Copy link
Member

What does this change

When we refresh the cached files for a bundle, delete the old directory so that any files that would not be overwritten, for example the updated bundle doesn't have a relocation mapping file or manifest, are removed.

What issue does it fix

Fixes #991

Notes for the reviewer

As a follow-up I am working on #992 since per the original issue, they are using porter explain which doesn't have a --force flag to make it easy for them to repull the bundle and use this fix.

Checklist

  • Unit Tests
  • Documentation - not impacted
  • Schema (porter.yaml) - not impacted

When we refresh the cached files for a bundle,
delete the old directory so that any files that would not be
overwritten, for example the updated bundle doesn't have a relocation
mapping file or manifest, are removed.
@carolynvs carolynvs merged commit 48d5f0c into getporter:master Apr 16, 2020
@carolynvs carolynvs deleted the clear-cache-on-refresh branch April 16, 2020 15:31
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.

Porter adding empty manifest to cache
3 participants