This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hello everyone! I am trying to login into a S3 compatible backend ( Dell ECS 3.6.2). I have received: • bucket url • bucket name • username • secret Which must be sufficient to integrate pulumi with the S3 backend. I have tried different scenarious. Has anyone tips, hints how to tackle this issue? My general idea was as stated in the documentation to do something like:

pulumi login 's3://<bucket-name>?endpoint=my.minio.local:8080&disableSSL=true&s3ForcePathStyle=true'

This message was deleted.

Is there a way to use podman with pulumi? Use case: 1. Have a podman (OCI) image get built (can be done outside of pulumi script if needed) 2. Push it to ECR 3. Use it as a lambda image

This message was deleted.

Hi! I am trying to setup Pulumi with Azure backend (Blob Storage) using az login from this documentation: https://www.pulumi.com/docs/concepts/state/#azure-blob-storage It is mentioned that "The Azure account must have the Storage Blob Data Contributor role or an equivalent role with permissions to read, write, and delete blobs." I have a contributor role on my account, and can manage blob storage and its containers, but I am getting: "RESPONSE 403: 403 This request is not authorized to perform this operation using this permission." Two questions: • Is Pulumi looking EXACTLY for this role to be assigned to the logged-in account? • Is it possible to setup this in a way, that only the READER role is required, so I could use Preview but not Up? (local machine development)