Built for Automation Not clicks
Rating: 8 out of 10
IncentivizedUse Cases and Deployment Scope
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
Likelihood to Recommend
The Google Cloud CLI shines when I need immediacy, discovery or targeted automation but is less appropriate when there is large scale infrastructure management. Using a series of Google Cloud CLI commands to build a production network is imperative. If the third command fails, I will be left with a half-built house and there is no easy way to roll back or know what state I am in.
CS
Chandra Shah
Systems and Test Engineer in Information Technology at NuPulse (11-50 employees)
Vetted Review
1 year of experience