Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify --region when deleting AlloyDB cluster #1602

Merged
merged 2 commits into from
Apr 4, 2023

Conversation

NimJay
Copy link
Collaborator

@NimJay NimJay commented Mar 17, 2023

Background

When I ran:

gcloud alloydb clusters delete ${ALLOYDB_CLUSTER_NAME} --force

I got the error:

ERROR: (gcloud.alloydb.clusters.delete) argument --region: Must be specified.
Usage: gcloud alloydb clusters delete CLUSTER --region=REGION [optional flags]
  optional flags may be  --async | --force | --help

For detailed information on this command and its flags, run:
  gcloud alloydb clusters delete --help

(I assume the default region used by gcloud alloydb clusters delete (in my environment) wasn't us-central1-b at the time at ran the command.)

Change Summary

  • Add --region=${REGION} to gcloud alloydb clusters delete command.

Testing Procedure

  • No testing necessary.
  • The screenshot below shows my change working:

Screenshot 2023-03-17 at 11 12 31 AM

  • If you want to be thorough, you can create an AlloyDB cluster and try deleting it — but this is overkill for this little change since the cluster can take 15 minutes to create.

@NimJay NimJay requested a review from a team as a code owner March 17, 2023 15:10
@NimJay NimJay merged commit 5b56b16 into main Apr 4, 2023
@NimJay NimJay deleted the nimjay-alloydb-delete-region branch April 4, 2023 19:40
mrcrgl pushed a commit to fiberfjord/microservices-demo that referenced this pull request Sep 11, 2023
)

Co-authored-by: Shabir Mohamed Abdul Samadh <7249208+Shabirmean@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants