little-plumber-23857
07/22/2025, 7:45 AMeager-twilight-23913
07/23/2025, 2:16 PMfast-sandwich-30809
07/24/2025, 3:06 PMimport
declaration from your program` .
If this resource was not under pulumi management, we would expect an import operation here. If this resource was managed, we would expect to see a delete operation in our previous runs, since our program hasn't specified it yet. I don't understand why pulumi thinks it was previously-imported (Is it pulling a backup of the statefile? Is it pulling from the checkpoint/history files?), and I also don't understand why the resource would need replacing.magnificent-eve-10499
07/24/2025, 3:36 PMkind-dinner-41259
07/25/2025, 1:22 AMrapid-parrot-24984
07/25/2025, 1:17 PMupgrade-provider
workflow:
error fetching organization teams: GraphQL: Resource not accessible by integration (organization.teams)
https://github.com/pulumiverse/pulumi-cpln/actions/runs/16513414410/job/46699662668#step:8:512
We believe we need help enabling read organization members and teams (read:org) permission for the GITHUB_TOKEN
in our Pulumi repository.fast-sandwich-30809
07/25/2025, 7:38 PMrefresh
and up
operations anytime there is an error. Normal operations work fine, but if there's a diagnosticEvent
with severity=error
(Ex. trying to create an Azure NSG rule that would conflict with an existing one), the pulumi process hangs. This started some time after <@UDNQQGNJF>/pulumi@3.177.0
, we started seeing it when we jumped to 3.183
and are still seeing it in 3.185
.
I'm not sure if the root issue is in the pulumi daemon, the node sdk, or the azure-native plugin. As far as I can tell, everything is "normal" (for an error condition, ex. I can read the event log) except control is not returned to our automation api wrapper (the promise doesn't resolve/reject). If I run manually / not through CI/CD I can see the dreaded infinite dotssparse-intern-71089
07/28/2025, 11:25 PMbored-dentist-51768
07/29/2025, 6:24 AMwide-twilight-48377
07/29/2025, 11:01 AMpulumi package add
stage.
I can't understand, what's wrong and how to fix it. Terraform is working with that provider totally fine. Panic log in the comment.modern-spring-15520
07/30/2025, 2:14 PMwitty-battery-42692
07/31/2025, 10:17 PMvictorious-gold-55753
08/01/2025, 1:31 AMhigh-grass-3103
08/01/2025, 10:51 AM${__dirname}/../assets/logo.png
. it's pointing to the same location, just didn't want a relative path. a side-problem is that it's Zitadel provider, which is a total mess, and it doesn't work. So I wanted to rollback.
Now when I run pulumi up
with the new path, the diff shows
~ zitadel:index/labelPolicy:LabelPolicy: (update)
[id=231695030580995897]
~ iconPath : "./assets/logo.png" => "${project root}/assets/logo.png"
but if DON'T approve, rollback the change in source code and run pulumi up
again, it shows
~ zitadel:index/labelPolicy:LabelPolicy: (update)
[id=231695030580995897]
~ iconPath : "${project root}/assets/logo.png" => "./assets/logo.png"
They can't be both right.
I can't refresh either because of https://github.com/pulumiverse/pulumi-zitadel/issues/31
I'm stuckdelightful-memory-59616
08/01/2025, 1:01 PMdelightful-memory-59616
08/01/2025, 1:08 PM~ taskDefinition: "arn:aws:ecs:us-west-2:---:task-definition/---:591" => [unknown]
delightful-memory-59616
08/01/2025, 2:13 PMwitty-dress-98303
08/01/2025, 7:23 PMpulumi up
, the preview is generated, but I do not see a prompt to on the action for the changes (yes, no, details). The process completes successfully shows the resources to be created.
I have started from scratch in Azure as well as recreated my pulumi stack. I am working in a sandbox environment, so it was not a big deal to delete the resources from Azure manually. I have tried running pulumi refresh
(successfully) and retrying with the same issue.
I have tried using the "-d" flag with no additional information.
Any thoughts?
UPDATE: I found the issue. Turns out I needed to update Pulumi. I managed to find a GitHub issue with a similar issue. When running echo $?
it returned 255. I did a brew upgrade pulumi (Macbook) and it resolved the issue.cool-tomato-73587
08/01/2025, 8:45 PMerror: could not create secrets manager for new stack: incorrect passphrase
name: provision infrastructure
on:
push:
branches:
- main
- dev
paths:
- 'infrastructure/**'
- '!infrastructure/shared/**'
pull_request:
branches:
- main
- dev
paths:
- 'infrastructure/**'
- '!infrastructure/shared/**'
workflow_dispatch:
jobs:
provision:
if: github.event_name == 'push'
name: Pulumi Up
runs-on: ubuntu-latest
defaults:
run:
working-directory: ./infrastructure
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '24'
- name: Install pnpm
uses: pnpm/action-setup@v4
- name: Install dependencies
run: pnpm install --filter ./infrastructure
- name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v4
with:
aws-access-key-id: ${{ secrets.PULUMI_AWS_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.PULUMI_AWS_SECRET_ACCESS_KEY }}
aws-region: ${{ secrets.AWS_REGION }}
- name: Pulumi Up
uses: pulumi/actions@v6
with:
command: up
stack-name: organization/project/${{ github.ref_name }}
cloud-url: ${{ secrets.PULUMI_BACKEND_URL }}
upsert: true
work-dir: ./infrastructure
env:
PULUMI_CONFIG_PASSPHRASE: ${{ secrets.PULUMI_CONFIG_PASSPHRASE }}
cool-tomato-73587
08/01/2025, 8:47 PMupsert: true
option creates the stack if not existing alreadyhigh-grass-3103
08/01/2025, 9:22 PMpulumi state move
command worked great, the biggest struggle I had was with my old resource structure.
Thanks, Pulumi team!sparse-gold-10561
08/05/2025, 7:06 PMwet-gigabyte-99270
08/06/2025, 12:17 PMboundless-artist-90671
08/06/2025, 1:12 PMhandsome-hamburger-88779
08/06/2025, 2:32 PM"message":"listing: unable to find any valid known_hosts file, set SSH_KNOWN_HOSTS env variable
However, I have provided the SSH_KNOWN_HOSTS to both to the helm release and in the stack manifest to deploy my program? Anyone as ever facing such issue?
More details in the ๐งต .modern-ghost-60077
08/06/2025, 8:09 PMsparse-intern-71089
08/07/2025, 10:36 AMrapid-parrot-24984
08/07/2025, 12:37 PMenablePullRequestAutoMerge
enabled for our repository?
https://github.com/pulumiverse/pulumi-cplnhigh-grass-3103
08/07/2025, 6:22 PMremote
provider, but that's more of an escape hatch (and then cloud-init
but only for initialization).
How about immutable distributions like NixOS (or just Nix)? They have well defined states and well defined state transition points, I think they should work great with pulumirough-ice-18151
08/08/2025, 5:28 PM{
"nameTable": {
"internal-smoketest-master": "urn:pulumi:internal-smoketest::byoc::components:iac:aws:QuestDBCluster$components:iac:aws:Instance::internal-smoketest-master"
},
"resources": [
{
"id": "eni-attach-0636431dce761a217",
"type": "aws:ec2/networkInterfaceAttachment:NetworkInterfaceAttachment",
"name": "internal-smoketest-master-nic-attch",
"parent": "internal-smoketest-master"
}
]
}
but I'm getting weird error when I try to import the resource:
โ bleh git:(fix-aws-nic-attachments) โ pulumi import -f import.json --preview-only --protect=false
Previewing import (internal-smoketest):
Type Name Plan
pulumi:pulumi:Stack byoc-internal-smoketest
Resources:
47 unchanged
error: anonymous.pp:12,10-35: undefined variable internal-smoketest-master;
Am I doing this right? It's taken me a bit of time to figure out the import file format and nametable structure. For context, the nic attachment is a child of a component resource, "Instance", which itself is a component resource of "QuestDBCluster"