ff95059748
Add new internal upload target for Google Cloud Platform and osbuild-upload-gcp CLI tool which uses the API. Supported features are: - Authenticate with GCP using explicitly provided JSON credentials file or let the authentication be handled automatically by the Google cloud client library. The later is useful e.g. when the worker is running in GCP VM instance, which has associated permissions with it. - Upload an existing image file into existing Storage bucket. - Verify MD5 checksum of the uploaded image file against the local file's checksum. - Import the uploaded image file into Compute Node as an Image. - Delete the uploaded image file after a successful image import. - Delete all cache files from storage created as part of the image import build job. - Share the imported image with a list of specified accounts. GCP-specific image type is not yet added, since GCP supports importing VMDK and VHD images, which the osbuild-composer already supports. Update go.mod, vendor/ content and SPEC file with new dependencies. Signed-off-by: Tomas Hozza <thozza@redhat.com>
18 lines
No EOL
789 B
Markdown
18 lines
No EOL
789 B
Markdown
# 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. |