[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Problem description
Using the GCS publisher I did not see a way of adding metadata to the GCS object.
This causes files to revert to default metadata, including the cache-control header, which is set to a 3600 second default cache.
RELEASES.json is affected by this header as well.
I want my cache-header to be set to no-store so that I can push updates instantly and not have to wait for cache to expire.
MarshallOfSound
commented
2 months ago
Pre-flight checklist
Problem description
Using the GCS publisher I did not see a way of adding metadata to the GCS object. This causes files to revert to default metadata, including the cache-control header, which is set to a 3600 second default cache. RELEASES.json is affected by this header as well. I want my cache-header to be set to no-store so that I can push updates instantly and not have to wait for cache to expire.
Attached is a pull request that adds metadata as a config option. https://github.com/electron/forge/pull/3682
Proposed solution
This pull requests adds a metadata option to the config of the GCS publisher. https://github.com/electron/forge/pull/3682
Alternatives considered
I can go into GCS and update the metadata after every publish but I would rather set this on the bucket upload itself.
Additional information
No response