Automated: Migrate {target_path} 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. 🚀
### 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).
### ⚠️ 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.
### 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!
#gsutil-migration
Signed-off-by: gurusai-voleti <gvoleti@google.com>
<!--
Thank you for proposing a pull request! Please note that SOME TESTS WILL
LIKELY FAIL due to how GitHub exposes secrets in Pull Requests from
forks.
Someone from the team will review your Pull Request and respond.
Please describe your change and any implementation details below.
-->
Fixes to readme for inaccurate guidance on setting Application Default
Credentials.
https://github.com/google-github-actions/setup-gcloud/issues/685
---------
Signed-off-by: eeaton <ellioteaton@gmail.com>
Based on github's comments in
https://github.com/actions/runner-images/issues/7101 it's my
understanding that at some point the system-installed gcloud will no
longer be included in the runners. When that happens, I assume any
workflows with `skip_install: true` will stop working
(also fyi: the readme
[references](https://github.com/google-github-actions/setup-gcloud#contributing)
CONTRIBUTING.md, but that file doesn't exist)
---------
Signed-off-by: Ethan Davidson <ethanmdavidson@gmail.com>
We have the GitHub-sanctioned starter workflows now, and these are
mostly unmaintained. Furthermore, for most of these, we would rather
have users use our other GitHub Action (like deploy-cloudrun) instead.
This adds support for specifying a version _constraint_ for the version
of gcloud. Since the GitHub Actions runners pre-install a version of
gcloud, this can dramatically reduce CI times.
* First pass of cleanup of old actions code
* fixed primary CHANGELOG file from setup-gcloud shift
* cleaning up old workflows
* removing working-directory spec as it's no longer needed
* Moar cleanup on the path to cleanup redemption
* "it now builds and tests pass locally"
* lint error cleanup
* More path cleanup
* addressing PR comments, more cleanup
* missed two files in last update
* Update README.md
Co-authored-by: Averi Kitsch <akitsch@google.com>
Co-authored-by: Thomas Osowski <osowskit@github.com>
Co-authored-by: Tom Osowski <osowskit@github.com>
Co-authored-by: Nick Van Wiggeren <nickvanw@github.com>
Co-authored-by: Brandon Keepers <bkeepers@github.com>
Co-authored-by: Nick Van Wiggeren <nickvanw@users.noreply.github.com>
Co-authored-by: Steve Winton <stevewinton@gmail.com>
Co-authored-by: Steve Winton <swinton@users.noreply.github.com>
Co-authored-by: Greg Orzell <gorzell@users.noreply.github.com>
Co-authored-by: Greg Orzell <gorzell@github.com>
