pulumi-community #general

general

broad-dog-22463

04/15/2021, 7:53 PM

we'd need to have an msi to do what we do with pulumi - it doesn't allow us to script moving binaries to bins and adding to PATH

broad-dog-22463

04/15/2021, 7:53 PM

it would need to be embeded in the msi

purple-train-14007

04/15/2021, 7:58 PM

Oh! yeah thats a "security issue" in msfts eyes.

purple-train-14007

04/15/2021, 7:59 PM

I would be surprised if they laxed that imo

purple-train-14007

04/15/2021, 8:00 PM

Fingers crossed though. MSFT has been opening up more and more to the community lately on certain things.

freezing-memory-87554

04/16/2021, 8:16 AM

Anyone? :-)

icy-jordan-58549

04/16/2021, 10:01 AM

error: getting user info from <https://api.pulumi.com>: performing HTTP request: Get "<https://api.pulumi.com/api/user>": dial tcp 37.57.111.6:443: i/o timeout

jolly-fountain-3864

04/16/2021, 2:43 PM

👋 I’m here! What’d I miss?

jolly-fountain-3864

04/16/2021, 2:44 PM

Question: How to I enable Https using Fargate and ECS with Pulumi ?

abundant-autumn-85033

04/16/2021, 5:30 PM

Ref; https://github.com/pulumi/pulumi/issues/3061 - someone suggested using module-alias as a polyfill for being able to use

@path/whatever

type notations within their pulumi programmes - has anyone got this working here? no matter what i try, it just can't find the modules.

brave-angle-33257

04/16/2021, 8:07 PM

im using a

for( var loop_var of ['a', 'b'])

loop in node, and in the loop i'm using a

stackreference.getOutput("outputs").apply(x=>x[loop_var])

and I'm getting the same results on subsequent loops, it's like it's not reapplying to give me the new value on the next loop, is this a known bug or some weird closure situation?

fancy-eye-43334

04/17/2021, 5:13 PM

Hey all, new to Pulumi here coming from a few years of Terraform usage. One of the problems I feel Terraform hasn't solved well yet is modeling necessary imperative steps within the declarative configuration. For example, if I need to run some script with inputs from the creation of a resource, and have another resource depend on that script's output, it's certainly doable but clunky. It seems like Pulumi is in a good position to solve these problems but there's nothing really native yet. The closest thing I could find is this provisioners strategy. I've used this now to create a couple of provisioners: an "S3StaticReactProvisioner" that runs yarn to build a client side react app with necessary environment config baked in, and then runs aws sync to S3; a "DBProvisioner" that ensures any necessary SQL setup is performed (depends on an RDS resource) prior to spinning up an ECS Fargate task that requires it; and I'm considering an Ansible provisioner as well. Of course I could have scripts that run pulumi + psql + ansible, or other strategies through code, but I want to maintain the declarative-first approach and rely on Pulumi for intelligent dependency management. Is Pulumi planning on expanding this concept? It seems like a great opportunity for people to build provisioners and publish them on NPM / other package distribution systems for others to take advantage of. Or are there limitations I don't understand yet that hinder this?

billowy-laptop-45963

04/18/2021, 6:23 PM

I have a component library. I created a simple example of one of the components and added to my examples_test.go and all was well. I add a more complex example and now pulumi up just hangs without error or any messages. Creating a new example with

pulumi new

and doing

pulumi up

works. The moment I

yarn link @mylib

(without even using it in the code)

pulumi up

hangs. Anyone seen this before?

billowy-laptop-45963

04/18/2021, 11:40 PM

When creating an acm.Certificate, for the validations I use to do something like

validations = [domainName, ...subjectAlternativeNames]
validationRecords = validations.map((domain, i) => new aws.route53.Record(`vr${i}`, { 
  name: cert.domainValidationOptions[i].resourceRecordName,
...
})

it seems like the aws.Certificate.domainValidationOptions[] ordering no longer matches my validations array. Is there a way to deterministically create the validation records?

billowy-laptop-45963

04/19/2021, 12:12 AM

My feeling is that I shouldn't create resources in another resources

.apply

eg:

cert.domainValidationOptions.apply(options=>options.map(option=>new aws.route53.Record(...

is that correct?

breezy-butcher-78604

04/19/2021, 3:26 AM

will PulumiUP be recorded and made available after the event? Keen to watch but it's not on at a good time for me

brash-airline-37413

04/19/2021, 7:18 AM

Sorry I’ve looked everywhere but and can not seem to find the answer anywhere. How do I compare an

Output<string>

with a

string

brash-airline-37413

04/19/2021, 7:20 AM

apply function only returns an Output<string> and there doesn’t be a way to resolve that promise any further

sticky-match-71841

04/19/2021, 11:52 AM

brew ugprade pulumi

supposed to install the 3.0 RC?

➜  services git:(develop) ✗ brew upgrade pulumi
==> Upgrading 1 outdated package:
pulumi 2.24.1 -> 3.0.0
==> Upgrading pulumi 2.24.1 -> 3.0.0 
==> Downloading <https://ghcr.io/v2/homebrew/core/pulumi/manifests/3.0.0>
######################################################################## 100.0%
==> Downloading <https://ghcr.io/v2/homebrew/core/pulumi/blobs/sha256:54d2d2d1823f55ae4951465619b11716a6177ee7d1c10a29751f366379556be4>
==> Downloading from <https://pkg-containers-az.githubusercontent.com/ghcr1/blobs/sha256:54d2d2d1823f55ae4951465619b11716a6177ee7d1c10a29751f366379556be4?se=2021-04-19T11%3A55%3A00Z&sig=bf3dGgi8X3ti%2FxR>
######################################################################## 100.0%
==> Pouring pulumi--3.0.0.big_sur.bottle.tar.gz
==> Caveats
zsh completions have been installed to:
  /usr/local/share/zsh/site-functions
==> Summary
🍺  /usr/local/Cellar/pulumi/3.0.0: 18 files, 134MB
Removing: /usr/local/Cellar/pulumi/2.24.1... (18 files, 142.6MB)

handsome-state-59775

04/19/2021, 12:09 PM

It seems the latest versions of

pulumi-tls

and

pulumi-azure-native

still depend on pulumi 2.x:

Could not find a version that matches pulumi<3.0.0,<4.0.0,>=2.15.0,>=2.20.0,>=3.0.0 (from -r <http://requirements.in|requirements.in> (line 1))
Tried: [...]
There are incompatible versions in the resolved dependencies:
  pulumi (from -r <http://requirements.in|requirements.in> (line 1))
  pulumi<3.0.0,>=2.15.0 (from pulumi-tls==3.4.0->-r <http://requirements.in|requirements.in> (line 2))
  pulumi<4.0.0,>=3.0.0 (from pulumi-kubernetes==3.0.0->-r <http://requirements.in|requirements.in> (line 4))
  pulumi<3.0.0,>=2.20.0 (from pulumi-azure-native==0.9.0->-r <http://requirements.in|requirements.in> (line 3))

Can we expect new releases for these with updated dependencies soon?

rhythmic-actor-14991

04/19/2021, 1:31 PM

const centralAlbAddress = centralIngress.status.apply(
    (status) => status.loadBalancer.ingress[0].hostname
);

worried-knife-31967

04/19/2021, 1:38 PM

I'm not sure if this was intentional or not... but using the pulumi github action as

@v2

the minimum CLI version is

2.25.0-alpha

. It seems strange the the v2 would require an alpha version of the SDK? I'm not sure whether this is github action semantics, but I'd expect

@v2

to be the latest stable version, not the latest experimental. This literally broke all my drift detections over the weekend 😠

broad-dog-22463

04/19/2021, 1:45 PM

This will be fixed in a pending release

broad-dog-22463

04/19/2021, 1:45 PM

It is indeed a bug that was introduced :/

broad-dog-22463

04/19/2021, 1:46 PM

This shouldn’t have broken anything though

broad-dog-22463

04/19/2021, 1:46 PM

Unless you were using a Pulumi cli version pre 2.25.0

worried-knife-31967

04/19/2021, 1:49 PM

2.22

worried-knife-31967

04/19/2021, 1:52 PM

I suppose upgrading a dependency is the bit that I'm worried about. What's the recommended syntax for the github action version to remain consistent with pulumi versions, but also opt-in to security/bug fixes?

broad-dog-22463

04/19/2021, 2:01 PM

so the issue you faced here (which wasn't well communicated on our part) is that the automation API is technically preview at this monent, so in order to get us to GA for it, we've been adding backward incompatible features with the CLI. We are now finished with that Upgrding the CLI should not force any dependency upgrades to your applications unless the Automation API requires a specific version. If you need to guard against upgraded CLI versions then you can change your CLI installation as follows:

- name: Install pulumi
  uses: pulumi/action-install-pulumi-cli@v1.0.2
  with:
    pulumi-version: 2.22.0

This is definitely the safest way for you to opt-in to changes

broad-dog-22463

04/19/2021, 2:02 PM

I definitely agree that this was unexpected behaviour