Hey everyone - finally got to the point internally...
# automation-api
Hey everyone - finally got to the point internally that we are now testing the Automation API portion of our in-house CD API. Having an issue that I thought had already been addressed but may be misremembering. Consistently getting the
error: PULUMI_ACCESS_TOKEN must be set for login during non-interactive CLI sessions
message. Trying to use a self-managed backend so I don't think I should be hitting this, or may be missing something. I currently have the backend set both in the project settings and in
I see a thread here https://pulumi-community.slack.com/archives/C019YSXN04B/p1619024754146000 about it but it looks like Ringo was using the pulumi service backend so he was able to just provide an access token
Any insight on this that I'm missing?
I don’t think so? I haven’t tried this in .NET, but in NodeJS, for example, I had no issues setting the backend via project settings (and don’t do anything with the env var)
Could it be that your backend URL is malformed? That could force the CLI to try and log you in to the service: https://github.com/pulumi/pulumi/blob/73a66f48ead301bacf1d7d2833c016cf803b57c1/pkg/cmd/pulumi/login.go#L128
I believe that was the issue. I was using local filestate for testing purposes and my path was
but when you use
in dotnet it uses back slashes instead of forward slashes, so pulumi wasn't liking that. Thanks guys!
partypus 8bit 1
@faint-table-42725 I've verified that it works in .NET.
🙏 1
👍 1