bitter-energy-677704/06/2023, 6:44 PM
worried-rain-7442004/06/2023, 6:47 PM
Specifically, is the pulumi cli a hard dependency to use the automation api?Yes, the Pulumi CLI is a hard requirement for AutoAPI. We're exploring long term approaches to removing this requirement, but it's definitely a ways off.
Is there a way to have state management completely self-contained in a Go binary? i.e. Is it possible pulumi to create an s3 bucket to use for state storage, and then proceed to provision a stack that uses that bucket as a state backend?Hmm... my answer is "yes and no" 😅 I would tackle this by creating a temporary directory (
), and using the filestate backend to write to that directory. From there, you can provision the stack, then delete the tmp directory.
and when I was done...
aws s3 mb <s3://my-bucket>
In this case, nothing about what I'm doing is "self-contained"; I'm invoking bash to run the aws command. Of course, you could use the AWS API from your Go program if you wanted. But unfortunately I don't think there's a way to "statelessly" bootstrap your environment.
aws s3 rb --force <s3://my-bucket>
bitter-energy-677704/06/2023, 7:03 PM