Hello, I want to create/manage stacks using Pulumi

automation API

using a Azure Storage Account. I can do this over pulumi CLI, but haven't found any docs/examples to do this over the Automation API, could someone be so kind to point it for me? Thank you!

You should be able to set the

backend

in the project settings I use S3 and KMS to encrypt the state. Here's an example in Python: https://github.com/kjenney/prov/blob/main/prov/common.py#L65-L69

@crooked-pillow-11944 Thank you very much! That was exactly what I was looking for, and I did make some progress on it. A new roadblock with this error, which was similar to what I got when the right envvariables were not set when using the CLI.

stderr: error: unable to open bucket <azblob://foobar>: azureblob.OpenBucket: accountName is required

This is my code snippet:

....
        backend_url = f"<azblob://foobar>"

        project_settings=auto.ProjectSettings(
            name=project_name,
            runtime="python",
            backend={"url": backend_url}
        )

        stack_settings=auto.StackSettings(
            secrets_provider=secrets_provider)

        workspace_opts = auto.LocalWorkspaceOptions(project_settings=project_settings,
                                                    secrets_provider=secrets_provider,
                                                    stack_settings={stack_name: stack_settings})

        stack = auto.create_or_select_stack(stack_name=stack_name,
            project_name=project_name,
            program=pulumi_program,
            opts=workspace_opts)
....

If it's anything like the AWS provider (and I think it is) I believe you pass these as environment variables when running the script

😄 all I had to do was

backend_url = f"<azblob://foobar/{accountname}>"

Once again, Thanks a lot @crooked-pillow-11944 !

@high-leather-15669 did you figure out what to do with the storage account key? I'd like to set it in the code rather than an environment variable

Hi @miniature-leather-70472 I could not find a way one can set this is in code, but rather only env variable 😞 I think this has to do with the go client that is using the env variable to dial out.

@high-leather-15669 thanks for the update

If you do find a different way, please do share 🙂 For the moment, for our case the env variable fits, but if can be done in code, I would prefer to do it this way too. But I couldnt find anything yet, and I think @crooked-pillow-11944 did the same. Don't want to go down that rabbit hole at the moment...