github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2025-02-09 15:27:11 +00:00
Code Issues Projects Releases Packages Wiki Activity
VictoriaMetrics/vendor/cloud.google.com/go/internal
History
Aliaksandr Valialkin 40f56fa93b
vendor: run make vendor-update 
Add exclude google.golang.org/grpc/stats/opentelemetry v0.0.0-20240907200651-3ffb98b2c93a to go.mod
according to https://github.com/googleapis/google-cloud-go/issues/11283#issuecomment-2558515586 .

This fixes the following strange issue on `make vendor-update`:

cloud.google.com/go/storage imports
        google.golang.org/grpc/stats/opentelemetry: ambiguous import: found package google.golang.org/grpc/stats/opentelemetry in multiple modules:
        google.golang.org/grpc v1.69.0 (/go/pkg/mod/google.golang.org/grpc@v1.69.0/stats/opentelemetry)
        google.golang.org/grpc/stats/opentelemetry v0.0.0-20240907200651-3ffb98b2c93a (/go/pkg/mod/google.golang.org/grpc/stats/opentelemetry@v0.0.0-20240907200651-3ffb98b2c93a)
2025-01-12 03:14:52 +01:00
..
optional app/{vmbackup,vmrestore}: add vmbackup and vmrestore tools for creating backups on s3 or gcs from instant snapshots 2019-11-08 21:21:07 +02:00
trace vendor: run make vendor-update 2025-01-12 03:14:52 +01:00
version vendor: make vendor-update 2020-11-13 13:09:09 +02:00
.repo-metadata-full.json vendor: run make vendor-update 2025-01-12 03:14:52 +01:00
annotate.go vendor: make vendor-update 2022-08-30 09:45:26 +03:00
gen_info.sh vendor: run make vendor-update 2024-06-24 23:08:47 +02:00
README.md vendor: run make vendor-update 2023-07-07 00:04:32 -07:00
retry.go vendor: run make vendor-update 2023-07-07 00:04:32 -07:00

README.md

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.