Error fetching service information from Docker: Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.

can you tell me what needs to be done to solve this error ?

Invalid syntax errors in pulumi_aws_native python source in 0.12.0 thru 0.15.0. Hi all, first time poster here. Making good progress with Pulumi elsewhere. I’m not using this specific functionality but it is causing a problem linting with mypy as I haven’t found a way of telling mypy to skip imports except in a global manner. I commented on an open issue (https://github.com/pulumi/pulumi-aws-native/issues/379) but haven’t seen an update there or information elsewhere. Thought it might be worth a post here. Thanks! e.g.

$ python3
Python 3.9.5 (default, Nov 23 2021, 15:27:38) 
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from pulumi_aws_native.acmpca import get_permission
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
 File "/usr/lib/python3.9/importlib/util.py", line 245, in __getattribute__
   self.__spec__.loader.exec_module(self)
 File "/home/mark/workspaces/.venv-pulumi-test/lib/python3.9/site-packages/pulumi_aws_native/acmpca/__init__.py", line 14, in <module>
   from .get_permission import *
 File "/home/mark/workspaces/.venv-pulumi-test/lib/python3.9/site-packages/pulumi_aws_native/acmpca/get_permission.py", line 54
   @_utilities.lift_output_func(get_permission)
   ^
SyntaxError: invalid syntax
>>>

Also revealed by mypy:

$ mypy .venv-pulumi-test/lib/python3.9/site-packages/pulumi_aws_native/

.venv-pulumi-test/lib/python3.9/site-packages/pulumi_aws_native/acmpca/get_permission.py:23: error: expected an indented block [syntax]

Found 1 error in 1 file (errors prevented further checking)

@pulumi.output_type
class GetPermissionResult:
   def __init__(__self__):
       

class AwaitableGetPermissionResult(GetPermissionResult):

Fix:

class GetPermissionResult:
   def __init__(__self__):
       ...

class AwaitableGetPermissionResult(GetPermissionResult):

Hi, I'm migrating from aws classic v4 to v5 and I'm having trouble with RDS insntace provisioning (https://www.pulumi.com/registry/packages/aws/api-docs/rds/instance/). On v5,

name

is deprecated and

db_name

is its replacement. If I just replace

name

with

db_name

while provisioning rds.instance, pulumi thinks I'm changing the value for

db_name

and plan to replace the instance. How can I just adjust the attribute (from name to db_name) without causing a replacement?

hello How do I get the current aws region set on the config?

Hi, I noticed the pulumi checksum & release do not match. Downloading from: https://github.com/pulumi/pulumi/releases/download/v3.29.1/pulumi-v3.29.1-linux-arm64.tar.gz I get a file with the checksum:

5f360484020169eea3e14bdb22be7acb29829c9082913b0c302e70ffff7aa0de

which does not match the provided checksum. However downloading from: https://get.pulumi.com/releases/sdk/pulumi-v3.29.1-linux-x64.tar.gz I get a file with the checksum:

54920bbba46613aef7b61769f477a3b8c9a667929001743ae827b29d959f1d32

which does match the provided checksum. I had this problem already in the past: https://github.com/pulumi/pulumi/issues/9063 Where it probably was due to the release process running twice and the cloudfront cache not being invalidated in between. As I refer to a specific pulumi version and checksum in my build system for the purpose of reproducible builds, this does block the update for me when it happens.

👋 Hi everyone!

Hey, granting a role to PostgreSQL on GCP gives connection failure. How it could be resolved?

Hi all - my team is getting started with Pulumi for managing a multi-cloud architecture that will include serverless, docker-based, and hosted services. does anyone have tips or best practices for CI/CD tooling that would be cloud and application agnostic enough to handle all of this under one pipeline?

Looks like there was a short hash added at the end of the name of the AKS cluster created by Pulumi. Is that expected behaviour?

I've seen how tags can be applied to a single resource - how would I apply an "owner" or "company" tag to every resource in the entire project? I would prefer not to specific a tags dict on every single resource. I'm under the impression this would help me work out detailed resource ownership / usage within Azure cost analysis (I could be wrong).

Questions for the maintainers, I understand that the Pulumi aws native modules are built automatically using

Pulumi SDK Generator

, whats the process to fix non-working generated modules ? ex: https://github.com/pulumi/pulumi-aws-native/blob/master/sdk/python/pulumi_aws_native/wafv2/get_web_aclassociation.py#L20 Missing retun for the function line

20

, and missing parenthesis line

47

? I’ve tried looking at the contrib docs but it doesn’t seem clear

Hello! I have a problem with

pulumi stack import

. I accidentally used the wrong AWS profile when creating a resource on my pulumi stack. Now pulumi thinks I’ve created a resource when it doesn’t exist in the AWS account that the stack is pointing at. I tried the following steps to fix this: 1.

pulumi stack export > stack.json

2. delete references to the resources I don’t want to have in the stack 3.

pulumi stack import --file stack.json

However, the

pulumi stack import

doesn’t seem to import my changes? I get no interesting output after doing step 3. When trying step 1 again (after having done step 3) I still see the references to the resources that I deleted in step 2. Has anyone else encountered this problem?

Hi, I have problem with

pulumi typescript

by creating

cloud run

everything seems fine. I almost got it right, except I got an error

gcp:cloudrun:IamMember (nodejs-everyone):
    error: 1 error occurred:
    	* No value was found for project during import

Here is my code about IAM config in pulumi ts

const iamNodejs = new gcp.cloudrun.IamMember('nodejs-everyone', {
  service: nodejsService.name,
  location,
  role: 'roles/run.invoker',
  member: 'allUsers',
});

What did I miss?

Hello, I was wondering if there is an estimate on when python will be supported in aws crosswalk for VPC creation, and is there a reason that languages besides nodejs weren't supported out of the gate like normal pulumi? Thanks

Hi all, CTO of Array.com here. Anyone from Pulumi can help me with business/enterprise pricing? I submitted the form but haven’t heard anything yet.

hello wonderful people! @sticky-planet-19341, one of Pulumi's ux designers, will be running some short interviews next week to gather some information to help improve the experience of using Pulumi. we are looking to talk with people who have lots of experience with Pulumi and with folks new to Pulumi, along with people somewhere in the middle. If you have 15 minutes to spare some time next week, please add an emoji to this message or thread a comment, and we will reach out to you to get you scheduled.

Hi All, I hope I’m in the right spot here, I’m having a hard time getting my azure function to work correctly and was hoping I might find some help here. I’m currently trying to create an azure function using pulumi/azure-native. The function code is written in python, (pulumi code is in TS). I’m trying to create a blob for the function web app to run from, The blob gets created but when the function is executed, I’m getting “module not found” errors for the dependancies I have defined in the

requirements.txt

file. The dir I’m using as the source for the blob follows the folder structure defined here. (https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-python?tabs=asgi%2Cazurecli-linux%2Capplication-level#folder-structure) What am I missing? How do I correctly create this blob so that the dependancies defined in requirements.txt get installed? Thanks in advance for any time you can take. Any ideas are appreciated.

I started a new gcp stack and created a new bucket, but now I suddenly get his unhelpful error message, which doesnt even specify which key is wrong or not existing

I triple checked everything, reset all the config etc, but it keeps giving me the same error msg no matter what... this is very frustrating

Hopefully an easy question. I'm looking to import a GCP Project's AppEngine using google-native. I tried the following:

pulumi import google-native:appengine/v1:App discovery-api bborie-sandbox

But I am doing something wrong...

Previewing import (dev)

View Live: <https://app.pulumi.com/dustymugs-atlasai/discovery/dev/previews/8d621b42-36e4-4b93-834d-01cd3315ff20>

     Type                               Name           Plan       Info
     pulumi:pulumi:Stack                discovery-dev             1 error
 =   └─ google-native:appengine/v1:App  discovery-api  import     1 error
 
Diagnostics:
  google-native:appengine/v1:App (discovery-api):
    error: Preview failed: property "appsId"/"name" not found
 
  pulumi:pulumi:Stack (discovery-dev):
    error: preview failed

What am I missing?

still an odd error, it would have been so helpful if the error described exactly which key was the offender

ok blaming yarn workspaces was wrong, I replicated the steps, everything working flawless until I add secret variables then something happens and it's totally tripping

removing everything back doesn't solve it and keeps on giving the same error as before

extremely strange

ok now I solved it I think, it seems to be a big no no to just remove variables by directly editing instead of using the cli? pretty sure that action was the offender

Does anyone know if the order of resources matter in the state file? I’m comparing state JSONs over time, and I’m finding that the resource order seems to change at random, not just when there are meaningful differences. It makes it harder to tell exactly what has changed between what I’m looking at. (I may implement my own sorting, if just to diagnose my issue, even if I don’t import the JSONs back.)

👋 Issue : Azure Native - Portal Dashboard - Invalid parsing metadata property This issue has been arise earlier this year i*n January* based on this PR-#1412, • We have shared the evidences and troubleshooting on the issue with the current API • The only fixes has to be done over Pulumi's end. Thus, I wish to escalate this incident up again 🙏