Built for Automation Not clicks
Overall Satisfaction with Google Cloud CLI
Being a medical device start-up we use Google Cloud CLI for infrastructure management mainly for setting up and configuring Cloud Storage buckets for storing medical imaging data, patient records, and log files and it enable the company to scale its infrastructure and applications as its user base grows.
Pros
- +544656
- chgvjvb
- kjhohij
Cons
- In some complex cases such as deploying PSC via CLI, I have seen instances where a command fails and does nothing without returning a clear error code or message
- A truly unified experience would be great to have where gsutil and bq are fully deprecated in favor of gcloud commands.
- Would be great to have a richer interactive model like the aws configure wizard
- Reduction in developer and DevOps time spent on cloud operations
- Automated resource creation and teardown reduced orphaned resources
- 5–15% reduction in monthly cloud costs due to better hygiene and automation
Google Cloud CLI stacks up well against other cloud and infrastructure CLIs by balancing power, consistency, and automation readiness, especially in production environments. Compared to AWS CLI, it’s more opinionated and readable, with better defaults and a more coherent command structure across services. Compared to Azure CLI, it’s less beginner-friendly but offers deeper control and is better suited for complex, large-scale workflows.
Do you think Google Cloud CLI delivers good value for the price?
Yes
Are you happy with Google Cloud CLI's feature set?
Yes
Did Google Cloud CLI live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Google Cloud CLI go as expected?
I wasn't involved with the implementation phase
Would you buy Google Cloud CLI again?
Yes

Comments
Please log in to join the conversation