[roll] Roll fuchsia [roll] Roll libc-tests Automated: Migrate fuchsia/libc-tests from gsutil to gcloud storage

This CL is part of the on going effort to migrate from the legacy "gsutil" tool to the new and improved "gcloud storage" command-line interface.
"gcloud storage" is the recommended and modern tool for interacting with Google Cloud Storage, offering better performance, unified authentication, and a more consistent command structure with other "gcloud" components. 🚀

⚠️ Action Required: Please Review and Test Carefully:

While we have based the automation on the migration guide, every use case is unique.
"IT IS CRUCIAL that you THOROUGHLY TEST these changes in environments appropriate to your use-case BEFORE MERGING."
Be aware of potential differences between "gsutil" and `gcloud storage` that could impact your workflows.
For instance, the structure of command output may have changed, requiring updates to any scripts that parse it. Similarly, command behavior can differ subtly; the "gcloud storage rsync" command has a different file deletion logic than "gsutil rsync", which could lead to unintended file deletions.

Our migration guides can help guide you through a list of mappings and some notable differences between the two tools.

Standard presubmit tests are run as part of this CL's workflow. "If you need to target an ADDITIONAL TEST WORKFLOW or REQUIRE ASSISTANCE WITH TESTING, please let us know."

Please verify that all your Cloud Storage operations continue to work as expected to avoid any potential disruptions in production.
Automation Details:

This change was GENERATED AUTOMATICALLY by an agent that targets users of "gsutil".
The transformations applied are based on the gsutil to gcloud storage migration guide - http://go/gsutil-gcloud-storage-migration-guide, external guide - https://docs.cloud.google.com/storage/docs/gsutil-transition-to-gcloud.

Support and Collaboration:

The "GCS CLI" team is here to help! If you encounter any issues, have a complex use case that this automated change doesn't cover, or face any other blockers, please don't hesitate to reach out.
We are happy to work with you to test and adjust these changes as needed.

Contact: gcs-cli-hyd@google.com

We appreciate your partnership in this important migration effort!
Original-BUG: b:486536908

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/libc-tests/+/1590129
Original-Revision: b995ff63d8a427be733e7094e96fbbc67c8ac850

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1592109
Original-Revision: 279a9ba25cf72bb62b081d4ebd28c6ca40cc81de
GitOrigin-RevId: 5fc6b02946cbb25ebe09a9e273f5b0b27bf21b32
Change-Id: I16fc710f6d015a54bb2f70109ba598168efef0f9
1 file changed
tree: 49bd0c38b4d63b4f06740b58641a21d38dc37b19
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.