This message was deleted.

sparse-intern-71089

03/14/2023, 4:55 PM

This message was deleted.

billowy-army-68599

03/14/2023, 4:58 PM

terraform refreshes by default, pulumi doesn’t. do

pulumi preview -r

acceptable-plumber-31485

03/14/2023, 4:58 PM

cool

acceptable-plumber-31485

03/14/2023, 4:59 PM

wow, it found the difference 🙂

acceptable-plumber-31485

03/14/2023, 4:59 PM

is it possible to use pulumi in command line to show the diff? That way, I don't have to login to the EC2 console

billowy-army-68599

03/14/2023, 4:59 PM

pulumi pre -r --diff

acceptable-plumber-31485

03/14/2023, 5:00 PM

also, it found another diff that I didn't update

acceptable-plumber-31485

03/14/2023, 5:00 PM

ah, it only showed 1 diff

acceptable-plumber-31485

03/14/2023, 5:01 PM

This was the first one

Copy code

(venv) ➜  iac-workshop-ec2-webservers pulumi preview -r
Previewing update (dev):
     Type                             Name                             Plan       Info
     pulumi:pulumi:Stack              iac-workshop-ec2-webservers-dev             1 warning
     ├─ aws:lb:TargetGroupAttachment  web-server-us-east-1d                       
 ~   ├─ aws:ec2:SecurityGroup         web-secgrp-sg                    update     [diff: ~ingress]
     ├─ aws:lb:TargetGroup            target-group                                
     ├─ aws:ec2:Instance              web-server-us-east-1e                       
     ├─ aws:ec2:Instance              web-server-us-east-1d                       
     ├─ aws:lb:TargetGroupAttachment  web-server-us-east-1b                       
     ├─ aws:lb:TargetGroupAttachment  web-server-us-east-1e                       
     ├─ aws:ec2:Instance              web-server-us-east-1f                       
     ├─ aws:ec2:Instance              web-server-us-east-1b                       
     ├─ aws:lb:TargetGroupAttachment  web-server-us-east-1a                       
     ├─ aws:ec2:Instance              web-server-us-east-1a                       
     ├─ aws:lb:TargetGroupAttachment  web-server-us-east-1c                       
     ├─ aws:lb:TargetGroupAttachment  web-server-us-east-1f                       
     ├─ aws:lb:Listener               listener                                    
     ├─ aws:ec2:Instance              web-server-us-east-1c                       
     └─ aws:lb:LoadBalancer           loadbalancer                                [diff: ~__defaults,enableCrossZoneLoadBalancing,subnets]

acceptable-plumber-31485

03/14/2023, 5:01 PM

there is another diff at the bottom row

acceptable-plumber-31485

03/14/2023, 5:01 PM

however, when I added

--diff

, it only showed the first one, the ingress

billowy-army-68599

03/14/2023, 5:01 PM

that’s just setting the values into state, you’ll notice it isn’t going to update the resource

acceptable-plumber-31485

03/14/2023, 5:01 PM

gotcha

acceptable-plumber-31485

03/14/2023, 5:03 PM

when this happens(for us in terraform), terraform will restore the original settings. I guess pulumi will restore it too

acceptable-plumber-31485

03/14/2023, 5:04 PM

i'll run pulumi up again

acceptable-plumber-31485

03/14/2023, 5:06 PM

oh, the manual change I made didn't get deleted. Pulumi up didn't delete it.

Copy code

Resources:
    17 unchanged

Duration: 4s

acceptable-plumber-31485

03/14/2023, 5:10 PM

I got it working using

refresh

acceptable-plumber-31485

03/14/2023, 5:10 PM

found this - https://www.pulumi.com/docs/reference/cli/pulumi_refresh/

billowy-army-68599

03/14/2023, 5:15 PM

adding

-r

pulumi up

is required as well

👍 1

acceptable-plumber-31485

03/14/2023, 5:18 PM

Because there is

pulumi up

and

pulumi refresh

, my experience in

terraform plan

and

terraform apply

is somewhat affecting my progress in learning pulumi. Currently at work, when we submit a merge request, our tooling called Atlantis does the terraform command behind the scene. If I will introduce pulumi to where I work(I'm sure I will because I'm loving it), what would be the Atlantis equivalent in pulumi? In a merge request, when we type

atlantis plan

in a comment section, it will run

terraform plan

or maybe it has it's own code. The output is the same. Once the merge request has been approved, we will type

atlantis apply

in the comment section, it will create the resources in AWS as well as merge the pull request.

billowy-army-68599

03/14/2023, 5:20 PM

There’s no comparative Atlantis like tool right now. You can achieve a similar experience using the GitHub app. Pulumi has update plans which operate similarly to terraform plan

acceptable-plumber-31485

03/14/2023, 5:20 PM

What about in Gitlab? We are using Gitlab.

acceptable-plumber-31485

03/14/2023, 5:29 PM

I reached out to Gitlab Support and I told them the scenario. Hopefully to hear a solution today so I can test

acceptable-plumber-31485

03/14/2023, 5:39 PM

ah, I see what you mean. I just found out that

pulumi refresh

didn't update the resources. When I ran

pulumi up -r

, that's only when it updated the resource.

billowy-army-68599

03/14/2023, 5:44 PM

there’s some integration with gitlab steps here https://www.pulumi.com/docs/guides/continuous-delivery/gitlab-ci/

acceptable-plumber-31485

03/14/2023, 6:02 PM

Oh cool, thanks a lot!

acceptable-plumber-31485

03/14/2023, 6:04 PM

ah, that's the one I followed few days ago. I got it working. It's different from what I want to accomplish

acceptable-plumber-31485

03/14/2023, 6:06 PM

in that document, we have to click a stage which will open another page in Gitlab. It shows the session in a gitlab-runner as well as commands that are in gitlab-ci.yml file being executed

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.