if i fix that it wants to deploy the whole cluster again

ah no worries i edited the state file and its ok

sshKeys: [{...}] --> sshKey: {...}

Im current transcribing our Cognito User Pool into Pulumi. The way I have done it is to use the terraform export tool which outputs a JSON state of the resource, then go line by line to transcribe each property.

In the tfstate there are properties that have a 0, which I assume is like a 'false' or 'unfilled' property like so:

I wanted our Pulumi objects to be more explicit and have every possible attribute. Would I just set the property in Pulumi to be false?

How do I change AWS Profile so that Pulumi can point to a different AWS account?

Hm, so I just created a Cognito User Pool through Pulumi, and I editted an attribute to be required from false to true. It deleted Cognito and made a Replacement. What If I wanted to change an attribute without deleting and replacing Cognito?

Hey guys, I have an urgent issue. I can't get the HorizontalPodAutoscaler working and I think its because it has a scaleTargetRef that wants me to specify a name for the deployment but the name from Pulumi has an autogenerated id on it which I think is cuasing it to not match the HPA to the Deployment

So I have literally the stupidest hack to make this work, but there has to be a correct way to do this...here is my hack...

I can't use 'id' on its own because its value is default/foo-d81n7khw

so i parse it, it works now

@early-intern-90238 are you unblocked for now? I don’t exactly follow what’s at the root of the problem here. If you set

name

explicitly then Pulumi will not auto name with a random postfix. It sounds like your worker did not specify a

name

?

Hm, we've got a CMS app with 24 Lambdas and associated API Gateways, Cognito, DynamoDB and RDS. Would it make sense to organize all infra in one stack? ANd use different stacks as different environments (dev, stage prod)?

Trying to wrap my head around how to use Projects and multiple Stacks under a project.

Ah nevermind, i will RTFM: https://pulumi.io/reference/organizing-stacks-projects.html 🙂

hi, perhaps i’ve missed it in the docs, but how to work with pulumi if you’ve already existing infrastructure created by terraform? is there an easy way to import it into pulumi state?

is there an example or schema for the --json preview output please?

Hi!

pulumi.output(azure.core.getClientConfig({})).apply(c => servicePrincipalObjectId)

is empty when I run pulumi on my dev pc. Is there a way to get the current user ID? I need to use it as

objectId

for permissions.

@white-balloon-205 any idea why creating a GKE K8S Ingress would be stuck like this?

++  ├─ kubernetes:extensions:Ingress  hello-kubernetes-us-east1         creating replacement..   [diff: ~metadata]; [2/3] Waiting for update of .status.loadBalancer with hostname/IP

A

pulumi up

failed and now I get several messages like this:

aws:elasticloadbalancingv2:LoadBalancer (e839e3dc):
    error: Plan apply failed: refreshing urn:pulumi:fib-autoscale::fib::awsx:x:elasticloadbalancingv2:ApplicationLoadBalancer$aws:elasticloadbalancingv2/loadBalancer:LoadBalancer::e839e3dc: Error retrieving ALB: ValidationError: 'arn:aws:elasticloadbalancing:us-west-2:710312645543:loadbalancer/app/e839e3dc-3597e49/e54545127f980ecc' is not a valid load balancer ARN
    	status code: 400, request id: e2522ac7-7d72-11e9-a259-a7fa9e6e25ad

How do you resolve this kind of error?

the JSON preview output is great, can now require approval for deploy right in the CI PR

error: cloudflare:index/zoneSettingsOverride:ZoneSettingsOverride resource '<zone>-zonesettings' has a problem: settings.0: invalid or unknown key: tls13
error: cloudflare:index/zoneSettingsOverride:ZoneSettingsOverride resource '<zone>-zonesettings' has a problem: settings.0: invalid or unknown key: tls12_only

Running into an issue with a CF ZoneSettingsOverride. Has anyone seen this before?

Not sure if it’s by design but noticed that if you run

pulumi preview --suppress-outputs --json

, the outputs end up in the JSON anyway

Hm, i'm using the JS sdk, what's a good way of organizing code? I currently have 3 Cognito user pools in 3 seperate files, require'd into the index.js . - Is this a good pattern? I'm planning to have the index.js be kind of like a 'Table of Contents' and put resources in their own folders to be require'd into the index.js.

I tried using io-ts but have run into the issues around how modules get packaged (https://github.com/pulumi/pulumi-aws/issues/249). Unfortunately, using an

await import

doesn’t work well as you typically declare your io-ts types globally. Also the

cloud-aws:functionIncludePackages: io-ts

doesn’t seem to change anything. Should I look at using custom packaging and import the assets or is there any other approaches I could try?

Is it at all (going to be) possible to go from TF to Pulumi without recreating all resources?

Hi people,. I am new on pulumi world. I have started to use terraform from a couple of months, and I would like to understand a little bit more the benefits, pros and cons with relation to pulumi and other things ... Currently I am working in a CI/CD pipeline on Azure DevOps, and I am going to certifying me in Azure DevOps, My daily work in with Kubernetes and some specific DevOps workflow, all using AZure Cloud platform and some other tools like terraform, helm, kong as a mesh service ... I would like to try pulumi, because python is a very powerful language, and I would like to use it, instead of YAML files, of course I want to continue using the other tools

What about infrastructure state in pulumi, Can I store it and manage it ?