Random question, but what's the difference between the `tls-self-signed-cert` package and using the `tls` package with

SelfSignedCert

?

This message was deleted.

Hello! In developing some custom python Components, I realized

register_outputs

does very little for sharing outputs of the Component. As discussed here: https://github.com/pulumi/pulumi/issues/2653. That’s fine and makes sense (kind of lol). My question is, is there actually anything wrong/dangerous with calling

pulumi.export(…)

within a Component, instead of in the main program, other than the Component consumer may not actually want that export?

I noticed some weird behaviour where the preview shows it’s going to create 10 resources, but the pulumi up only creates 6. Does anyone know why this could be?

Hi everyone, I have pretty much all my Snowflake config run by pulumi, but the snowflake.Share provider is causing me issues: as mentioned in terraform [here](https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/555) creating a share relies (needlessly imho) on creating a "temporary" database and granting usage on it to the share. Once that is done, it causes all sorts of issues and you have to manually revoke the grant on that database before you can do anything useful with the share. Does anyone have a recipe to prevent this temp_<whatever> database creation and binding to the share (why not being able to specify what DB to use in the config, i wonder?) As a last resort, can I issue some custom SQL to manipulate the share in a more normal way (maybe wrapping the Share object in something that would allow me to fire a statement pre/post to clean up this mess?)

Hello community, I've imported some cloud resources using

pulumi import

with yaml runtime, then I've created and applied

kind: Program

and

kind: Stack

with the generated yaml. Pulumi kubernetes operator is trying to re-create the resources instead of detecting it from the provided s3 state. Pulumi kubernetes operator log:

AlreadyExists: AutoScalingGroup by this name already exists

The security group 'some-sg' already exists for VPC 'vpc-some-id'

"Cluster already exists with name: some-eks-cluster-name"

ResourceAlreadyExistsException: The specified log group already exists

Hello all, I’m trying to create a CRD for Crunchydata Postgres, I have the CRD but is impossible to convert using crd2pulumi. I’m having an error in the definition and I can’t understand how to fix, any advice?

We're having a weird issue where our Pulumi stack previews and deploys fine on a local machine but when running in the GitLab CI both

pulumi preview

and

pulumi up

hang indefinitely and the Pulumi Service shows that the update failed but with no error message. It seems like some sort of disconnection happens near the end of both preview and up. Any tips or help?

Hi Team, We are trying to run pulumi program inside azure K8 pod. We are configurating pulumi state in Azure blob. We are using azure native provider to provision resources. To authenticate azure blob from K8 pod, we are planning to use workload identity. Can we know if there is any support for workload identity in Pulumi? If not, is there any way where we can pass the credentials to Pulumi program?

I find myself having to manually do a

pulumi state delete $urn

when ever I update a secret, Pulumi tells me everything was okay creating a new and deleting the old secret, but every time it only deletes the secret without creating the new one. After removing it from the state it works as expected (until next time I change secrets) https://www.pulumi.com/registry/packages/github/api-docs/actionssecret/

Has anyone used pulumi in order to provision on demand stacks from within an application? I have a pretty simple application that I want to deploy that will essentially have a different JSON configuration that users of my application will be able to configure. Is this something pulumi can handle? How would I go about calling the pulumi up command from within the context of my backend?

Hi, is there a way to import existing gcp resources using pulumi automation api? Any example/ideas/advice/etc will be greatly appreciated.

Is a Config() supported inside a Jupyter notebook? I create k/v from the command line and it never seems to be able to find them when reading them in a cell. I did find the option to specify the venv environment I'm using but that didn't seem to help.

Config(None) also doesn't work .. claims it needs a string.

Language: Python (for those who don't know what a Juptyer notebook is)

Hi, wondering if it's possible to get a pulumi secret out of the config when when not using

pulumi up

? The use case I have is wanting to get a secret that's in the pulumi config to use an playwright tests . But for the life of me can't get it working. when using

new pulumi.Config()

it seems to create a new config instead of loading an existing config? And I have no idea how to load the correct stack config programmatically (TypeScript) with code not run via

pulumi up

. I've spent the afternoon googling and read docs but havent gotten anywhere appreciate any help/guidance.

Hey all, I'm struggling while using a new Terraform Bridge provider I've built -- looks like there's a timestamp that returns a date and time, but the format Pulumi is using to detect that is only looking for a date, which is breaking resource creation.

I am not entirely sure how to reproduce yet, but it appears Pulumi has managed to get out of sync with itself (only one github action runs it), and it has the diff for an update wrong. It wants to remove what I want to add, and correctly in AWS the state reflects what Pulumi wanted to remove. Looking at the Pulumi scripts, they clearly agree with me, not Pulumi. I have no idea whats going on, but currently I have a hard time trusting the state managed by Pulumi. Has anyone seen anything similar? Could it potentially be a problem where a github action times out or something and appears to have successfully completed, but the state was not completely transferred to the pulumi service?

Hi there! I sent a (relatively small) pull request a bit over a week ago, and haven’t heard anything back yet. Is there anything I can do to help it along? https://github.com/pulumi/pulumi/pull/12261

I created some resources using azure-native provider, I configured the location for the provider, now I changed the way of creating the resources so I set the location directly on the resource (it is not taken from the provider configuration). Pulumi now wants to replace the resource because of the location changed from

UK South

to

uksouth

even though the provider was before also configured to

uksouth

. Any help here? What can I do? I tried to export the stack, change the location manually and import it back, but the problem remains. When I refresh the stack, it also returns back to

UK South

Quick question, if I use

pulumi new

and the project already exists, will it overwrite this project completely or just update if there are changes, as

pulumi up

does?

Hey all. I had a situation that I can't figure out currently. I'm trying to create a policy to review AWS S3 buckets. I want to guarantee that a bucket always has a matching BucketPublicAccessBlock resource with that bucket associated with it. It's important that it not use stack validation, but resource validation (Don't want the buckets created without the proper policies). I figured you could use validateResourceOfType and then compare it with the other resource to see if they both exist. However, I haven't been able to find a way to compare 2 different resources. Kind of an "and" condition policy. Any ideas from the community?

Hello All- I am using a forEach call in typescript to deploy 20 services. The problem is that each independent service is deployed sequentially. We don't set the parallel option when we run pulumi up. Is there a way to deploy the services in parallel?

Hi all, Looking at the comments to me it seems like the recommend way of implementing a backend is to configure it in

Pulumi.yaml

instead of using the environment variable

PULUMI_BACKEND_URL

. Is this correct ? This would have the limitation of having one backend

per project

and cannot have one

per stack

. If I only have a backend per project in the

Pulumi.yaml

file and that backend is stored in

S3

AWS Account

1111111

but each

stack

[*dev*|*stage*|*prod*] is per AWS Account `222222`|`3333333`|`4444444` how do I configure `Pulumi`/`Github Actions` to use AWS Account

1111111

for the backend operation but deploy the resources in the case of dev in AWS Account

222222

? At the moment i have the following in

GitHub actions

but this only works if the backend and the resources been deployed are in the same AWS Account:

- name: Configure AWS Credentials

uses: aws-actions/configure-aws-credentials@v1-node16

with:

aws-region: ${{ env.AWS_REGION }}

role-to-assume: ${{ secrets.AWS_DEV_PULUMI_ROLE }}

role-session-name: OIDCSession

- name: Deploy changes to Infra

uses: pulumi/actions@v4

with:

command: up

stack-name: ${{ env.PULUMI_DEV_INFRA_STACK }}

work-dir: ${{ env.PULUMI_DEV_INFRA_CWD }}

env:

PULUMI_CONFIG_PASSPHRASE: ${{ secrets.PULUMI_INFRA_DEV_ACCESS_TOKEN }}

Hey everyone, I wondered if there was any existing best practice for or a best place to direct a question about publishing a typescript library for dynamic resource providers?

Beginner question: can Pulumi fully manage a GitHub repo's settings? I played with the github provider today, but when I import my test GitHub repo, it doesnt seem like its picking up all of the GitHub repo settings, like the branch protections. Am I missing something, or, does the github provider lack the ability to import all of the settings?

Did something happen to the plugin downloads? Since a few hours some of our builds are failing because https://get.pulumi.com/releases/plugins/pulumi-resource-twingate-v0.0.32-linux-amd64.tar.gz just returns 403s (seemingly from s3).

Can we use Pulumi to enable APIs on GCP?

Any commentary on Supabase and Pulumi (TS), either independently aboutb supabase or pointers on how to deploy them together? Trying to figure out what my auth and database story looks like...