4 ms·
Our thesis is that GCP's UI is not discoverable. Could you elaborate if by "discoverable" you mean these have been non-issues for you? 1) billing is aggregated
by diceduckmonk 4y ago
Our thesis is that GCP's UI is not discoverable. Could you elaborate if by "discoverable" you mean these have been non-issues for you?
1) billing is aggregated at too high of a level. Teams have to decompose services into projects, which proliferates the other "discoverability" problems.
2) Search misses a lot
3) Byzantine directory structure and navigation
4) Docs are just broken
5) Parts of GCP UI hint at the equivalent REST payload for API payloads, but this is hit or miss.
Or did you intend that the UI->CLI is relatively more discoverable than AWS/Azure. We've found Azure's search and UI to be surprisingly decent. AWS' console is fragmented but their docs are great.
- busterarm 4y agoYou have to be careful using the UI vs CLI/Terraform as you will get inconsistent results. For example, enabling any API via the UI will also create any "glue" service accounts in your project that are expected for that API to operate (for example, Compute API and the default compute service account). If you were to enable the Compute API via Terraform, it will NOT create the default compute service account -- you will need to do that with a separate terraform resource. There are tons of quirks related to operating GCP but not significantly moreso than other cloud providers.