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.

Sign up for GitHub

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

Jump to bottom

feat(gatsby-source-s3): Leverage Cache API #159

Open
Vacilando opened this issue Feb 1, 2022 · 2 comments
Open

feat(gatsby-source-s3): Leverage Cache API #159

Vacilando opened this issue Feb 1, 2022 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@Vacilando
Copy link

Can we better leverage Gatsby Cache API so that the pulled images persist between builds?

This is to continue the discussion from a previous incarnation of this module, see gatsby-uc/gatsby-source-s3#16 (comment)
@Vacilando Vacilando added the enhancement New feature or request label Feb 1, 2022
@moonmeister moonmeister added the help wanted Extra attention is needed label Feb 1, 2022
jbolda pushed a commit that referenced this issue Jan 28, 2023
@renovate @renovate-bot @jbolda
Update gatsby monorepo (#159)
b15b57b 
Co-authored-by: Renovate Bot <bot@renovateapp.com>
@konsalex
Copy link
Contributor

konsalex commented Mar 4, 2023 •
edited

Hey folks any progress on this? I can see myself cache is wiped after every gatsby develop run:

image

Is there any workaround on this, or it should be included in plugin's source code?

PS: I am using the source-strapi plugin

@moonmeister
Copy link
Contributor

This issue is for the s3 plugin. But no progress, PRs are welcome for any plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Vacilando @moonmeister @konsalex