I have an issue with create the api schema in azure api management

anyone can help me?

Good morning!

Wondering if the "configConnectorConfig" property in the gcp cluster addon does all the configuration necessary for the add on to work, of if the rest of the steps in this guide must be performed manually? https://cloud.google.com/config-connector/docs/how-to/install-upgrade-uninstall#add-on

Reason I am asking is that after enabling it and deploying some gcp custom resources, even though the resources are created in kubernetes, they do not seem to create a counterpart on GCP

no errors either, so not sure where I should look at.

How can i get programmatically cloud config? For example

gcp:region

or

aws:region

Thanks @millions-microphone-64941 for sharing this

Is anyone successfully in obtaining a more verbose debug log? I was expecting the following

export TF_LOG=TRACE
pulumi refresh -v 9 --yes && pulumi up --yes -v 9

to work for me but it didn’t

Is pulumi support deploying docker containers ? Any reference / link? I have a running remote docker host and want to deploy containers on that host using docker API with pulumi

I'm running into what looks like a deadlock situation. Does anyone have recommendations on how to debug a situation like that? Relevant code here: https://github.com/mitodl/ol-infrastructure/blob/dagster_instance/src/ol_infrastructure/infrastructure/applications/dagster/__main__.py

So, is there really no way to associate a docker image with a Google Compute Engine instance using pulumi? I asked last night but got no answer.

Hey Guys, i'm trying to use provisioners with CopyFile and changeToken but when i edit the file and want to copy again pulumi doesn't detect any changes. anyone got sugguestions for troubleshooting steps?

Quick question… we got sometime error when executing pulumi inside our cicd pipeline with gitlab-ci.

ERROR: Job failed (system failure): error dialing backend: dial tcp 10.135.14.46:10250: connect: connection refused

I wanna know if that’s normal that pulumi trying to reach the kubelet?

@big-potato-91793 what kind of resource are you trying to deploy?

Is there an established pattern for organizing stacks into smaller substacks?

👋 general question about plugins. I manually install the versions of the plugins that i want, by doing:

pulumi plugin install resource aws v3.2.0
pulumi plugin install resource kubernetes v2.4.3

But sometimes when I then run

pulumi up

, pulumi starts installing different versions of the same plugins..

pulumi up
Previewing update (dev):
[resource plugin aws-3.2.1] installing
Downloading plugin: 0 B / 68.86 MiB [----------------------------------]   0.00%
[resource plugin kubernetes-2.5.0] installing

Can I disable that? Where is it configured?

if I have a multi-file node project (multiple local modules), in a Lambda setting, what's the proper way to have Pulumi deploy them along with the definition of the Lambda callback?

Hey guys, I think I have hit an infinite recursion problem, activating the service usage API fails with pulumi because… well because the service usage API has not been activated yet!

gcp:projects:Service (EnableServiceUsage):
Step #9 - "Pulumi Create Stack":     error: Error when reading or editing Project Service : Request "List Project Services my-project" returned error: Failed to list enabled services for project my-project: googleapi: Error 403: Service Usage API has not been used in project XYZ before or it is disabled. Enable it by visiting XYZ then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry., accessNotConfigured

sup guys trying to launch test example of aws sns on empty project with the latest libraries, has panic accessing nil (golang): https://gist.github.com/afoninsky/250c1dbb96ff00ceaa2d830f0535fc93 I wonder if somebody met similar behaviour?

I'm running into an issue with creating a Vault database connection due to errors with parsing the connection URL. I'm not sure if it's because I'm trying to pass in the host_url as an Output object and it's not resolving before trying to pass it to Vault?

db_config.db_connection = 'postgres://{{db_user}}:{{db_pass}}@{{db_host}}:{{db_port}}/{{db_name}}'        
self.db_connection = database.SecretBackendConnection(
            f'{db_config.db_name}-database-connection',
            opts=resource_opts.merge(ResourceOptions(parent=self.db_mount)),
            backend=db_config.mount_point,
            verify_connection=db_config.verify_connection,
            name=db_config.db_name,
            data={
                'username': db_config.db_admin_username,
                'password': db_config.db_admin_password,
                'db_host': db_config.db_host,
                'db_port': db_config.db_port,
                'db_name': db_config.db_name
            },
            **{db_config.db_type: {
                'connection_url': db_config.db_connection
            }}
        )

The host_url is the

address

attribute of a created RDS instance.

say you have a large pulumi project and something goes bananas, it happens not very often but sometimes. You need to export the stack, remove pending operations but then you may remove operations that other resources are dependant on and you end in a loop that takes hours to solve. Is there are faster way? can I just remove manually all resources and then tell pulumi to start from clean slate?

There's apparently something called

lifecycle

which for example could let me specify "*don't* delete this VM when

user_data

changes", but the only mentions of it I found are in https://www.pulumi.com/docs/reference/pkg/aws/ec2/launchconfiguration/ which points to https://www.terraform.io/docs/configuration/resources.html. So how does one specify this? (in python, if that makes a difference)

Hi everyone. I tried to change my stack passphrase and now I'm getting the following error:  

Preview failed: unable to discover AWS AccessKeyID and/or SecretAccessKey

I'm not being able to fix this issue, I reviewed my .aws/credentials and .pulumi/credentials but no idea. Any idea?

How does Pulumi detect changes with FileArchive/AWS Lambda function resoruces? Every time I do a deployment in a CI/CD pipeline all lambdas redeploy regardless of if the actual content has changed. Looking to find a way around this.

I am deploying docker container on our docker host which support docker API version 1.39 but not latest one. From docker cli, we can set version and can connect to docker host.

export DOCKER_API_VERSION=1.39

However with pulumi, its not working There is no option to set API version https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/docker/config/ When deploy with pulumi I am getting error

error: Error pinging Docker server: request returned Internal Server Error for API route and version <https://DNS>:PORT/_ping, check if the server supports the requested API version`

I am using below config with pulumi

docker:host: "<tcp://DNS:PORT>
docker:certPath: "valid path to docker-cert"
docker:tlsVerify: 1
docker:apiVersion: 1.39

Any help here?

our docker host do not support latest version 1.40 so how can I set lower API version in Pulumi

➜  mta git:(pulumi) ✗ export DOCKER_API_VERSION=1.40
➜  mta git:(pulumi) ✗ docker ps
Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.39
➜  mta git:(pulumi) ✗

Hey, I have a scenario of a production environment with many single tenant EC2 based copies of our application. Each instance is a different tenant. Couple of questions: • Design-wise, would I create a stack for each one or one big stack for all? • If the first is prefered, what is the best way to create and update multiple stacks at once?