0eb465782a
Updates: - unpin AWS dependencies and run `make vendor-update` - add config options to enable checksums only if required by storage in order to preserve backwards compatibility Related issues: - https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9748 - https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8622 Tested with: AWS S3, self-hosted MinIO, Linode object storage as it was failing previously with multi-part uploads (reported here - https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8630#issuecomment-2772185033). An updated library allows (PR with the fix - https://github.com/aws/aws-sdk-go-v2/pull/3151) overriding multi-part upload configurations so that compatibility can be preserved. Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com>
Internal
This directory contains internal code for cloud.google.com/go packages.
.repo-metadata-full.json
.repo-metadata-full.json contains metadata about the packages in this repo. It
is generated by internal/gapicgen/generator. It's processed by external tools
to build lists of all of the packages.
Don't make breaking changes to the format without consulting with the external tools.
One day, we may want to create individual .repo-metadata.json files next to
each package, which is the pattern followed by some other languages. External
tools would then talk to pkg.go.dev or some other service to get the overall
list of packages and use the .repo-metadata.json files to get the additional
metadata required. For now, .repo-metadata-full.json includes everything.
Updating OwlBot SHA
You may want to manually update the which version of the post-processor will be used -- to do this you need to update the SHA in the OwlBot lock file.
See the postprocessor/README for detailed instructions.
Note: OwlBot will eventually open a pull request to update this value if it discovers a new version of the container.