I do have a question that I'm probably putting in the wrong spot, but I just ramped up a quick GraphQL endpoint on AWS, and I didn't write down the API Key anywhere... I just made it go up... now Houdini wants me to supply it as a 'bearer token' because it obviously didn't have any access to do a call to the endpoint... so I logged into the stack on Pulumi, and it's very ahh... lots of tokens and stuff. Key appears to be two UUID's and then ciphertext: and a ... JSON?

■  If you need to pass headers, add them after the URL (eg: '<http://myurl.com/graphql> Authorization=Bearer MyToken')

It's like, two keys and one ciphertext instead of what I expected... an actual AWS API Key

It might be an output of the resource If it is I think you can get the output using the CLI, there is a cryptographic key created for every stack automatically if you store them in pulumi cloud and the CLI will automatically use it to get the information you're trying to get, at least that's how it works for configs, I can't remember off the top of my head if it works for outputs like that

I’ve managed to get the apiKey but it doesn’t seem to be used the same way any other API is, because Authorization=Bearer key doesn’t work. I’ll have to find out how AWS does it and set up Houdini manually.