damp-magazine-5970709/26/2023, 9:29 PM
field must have the numeric project ID • The "Workload Pool ID" and "Identity provider ID" fields must each have just the short ID, not the fully-qualified
. that's definitely what this comment says, i just didn't follow it. some help text on this would be super helpful....
lemon-agent-2770709/27/2023, 5:02 PM
damp-magazine-5970709/27/2023, 5:41 PM
attribute." IOW: "figure it out bro." getting claims right is touchy and important, especially when you're probably dealing with full cloud admin; there should at least be some examples, not just a pointer to the reference docs 4. the fact that the instructions are all point-and-click console instructions to set up an IaC system is a little silly. these are useful and should exist but a set of pulumi scripts (even just sample scripts that require customization) would be far, far more useful. for instance, even once i'd figured out which workload provider ID to use, figuring out which ID and/or name attribute of the object to use in Pulumi was another trial-and-error process. (in part this is GCP's fault, for having so many different identifiers, but the docs could make it easier.) having an example to start from for plumbing together the various OIDC bits with Deployment Settings would have saved me a bunch of time and frustration. 5. literally every code snippet at https://www.pulumi.com/registry/packages/gcp/api-docs/iam/workloadidentitypoolprovider/#workloadidentitypoolprovideroidc appears to be copy-pasted from the same unrelated source. none of them are even vaguely related to the documentation, some are just
, and they're a mix of at least three or four different languages. 6. the docs should actually exist, unlike here for instance this took me a few days to get right so there are probably other things, but these are the bits that stand out in my memory