Skip to content

[usability] some APIs require project # rather than project #688

@bcoe

Description

@bcoe

The Cloud Secrets Manager API requires that a user provide their project #, rather than their project name. This information is buried deep in an account, and creates a real usability hiccup for users, ideally:

  1. a project or project # would be optional, and we'd detect the appropriate value.
  2. if we see a project provided for parent, rather than project #, we'd translate it to the project # (is this possible?).

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.triage meI really want to be triaged.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions