Hello, qq: is there a way to output preview details to a file? I'm having a pretty big diff and running out of scroll

createNodeGroup

on a

eks.Cluster

takes an

instanceType

parameter which must be a

aws.ec2.InstanceType

. I'd like to pass in a string from a config file. How can I do this without Typescript complaining?

I’m getting the following error when using the Pulumi Azure DevOps release task to run pulumi up:

2019-08-05T19:10:09.1841769Z ##[section]Starting: Run pulumi  
2019-08-05T19:10:09.1845138Z ==============================================================================
2019-08-05T19:10:09.1845233Z Task         : Pulumi Azure Pipelines Task
2019-08-05T19:10:09.1845346Z Description  : Azure Pipelines task extension for running Pulumi apps.
2019-08-05T19:10:09.1845410Z Version      : 0.1.19
2019-08-05T19:10:09.1845509Z Author       : Pulumi
2019-08-05T19:10:09.1845565Z Help         : Join us on Slack at <https://slack.pulumi.io>.
2019-08-05T19:10:09.1845633Z ==============================================================================
2019-08-05T19:10:09.3946841Z Downloading: <https://get.pulumi.com/releases/sdk/pulumi-v0.17.27-linux-x64.tar.gz>
2019-08-05T19:10:09.7313899Z Extracting archive
2019-08-05T19:10:09.7348031Z [command]/bin/tar xzC /home/vsts/work/_temp/1ad4480f-4b59-4fed-9e58-4f008e359445 -f /home/vsts/work/_temp/5888e3ed-db52-4523-9c13-87a924a0050d
2019-08-05T19:10:10.8380108Z Prepending PATH environment variable with directory: /home/vsts/work/_temp/1ad4480f-4b59-4fed-9e58-4f008e359445/pulumi
2019-08-05T19:10:10.8388818Z [command]/home/vsts/work/_temp/1ad4480f-4b59-4fed-9e58-4f008e359445/pulumi/pulumi version
2019-08-05T19:10:10.9270755Z v0.17.27
2019-08-05T19:10:10.9325912Z [command]/home/vsts/work/_temp/1ad4480f-4b59-4fed-9e58-4f008e359445/pulumi/pulumi login
2019-08-05T19:10:11.4999524Z Logged into <http://pulumi.com|pulumi.com> as mike (<https://app.pulumi.com/mike>)
2019-08-05T19:10:11.5044407Z [command]/home/vsts/work/_temp/1ad4480f-4b59-4fed-9e58-4f008e359445/pulumi/pulumi stack select mike/microservice-aks-deploy/mapper
2019-08-05T19:10:12.3840915Z [command]/home/vsts/work/_temp/1ad4480f-4b59-4fed-9e58-4f008e359445/pulumi/pulumi up --yes
2019-08-05T19:10:13.3621045Z Previewing update (mapper):
2019-08-05T19:10:14.2525744Z error: could not load plugin for kubernetes provider 'urn:pulumi:mapper::microservice-aks-deploy::pulumi:providers:kubernetes::inflation_provider': no resource plugin 'kubernetes' found in the workspace or on your $PATH
2019-08-05T19:10:14.2611968Z ##[error]Pulumi command exited with code '255' while trying to run 'up --yes'.
2019-08-05T19:10:14.2686239Z ##[section]Finishing: Run pulumi

Any ideas on how to fix this?

I'm using pulumi to create aws cognito user pool and associate it with lambda trigger. But every time the lambda function update, it'll re-create cognito user pool and all users store in it will gone. Does anyone knows how to fix it ?

Does pulumi run in its own shell? For example

AWS_PROFILE=lykke ./build-local.sh && cd ./artifacts/infra && pulumi up --yes

fails with an error about aws access key yet if i run each command separately it works fine

If I create a script called `test.sh`:

#!/bin/sh
echo "_$BOB"

And run

./test.sh && BOB="a" ./test.sh && ./test.sh

The output is:

_
_a
_

If you really don’t want to

export

AWS_PROFILE

so it’s available to all the subsequent commands you can do this instead:

AWS_PROFILE=lykke sh -c './build-local.sh && cd ./artifacts/infra && pulumi up --yes'

Hi, Google raised a security issue with us regarding a GCP service account which had been compromised and the key had been found here: https://www.bountysource.com/teams/pulumi/issues. The issue no longer exists so I need some assistance understanding what the issue was. This service account is encrypted in my Pulumi scripts but I use GCP storage for backend.

is there a way to bypass serialization of the callback in

lambda.CallbackFunction

in test mode? still digging, but it looks like adding that resource is increasing our test run time by 7x

People, how do you run pulumi in CI/CD? Examples given in docs are unpractical, no way I am installing nodejs and rebuilding node-grpc on every pulumi run 🙂

I think I'll commit node-modules to git and call it a day

You can always use the pulumi docker image.

Or setup caching in your CI system.

I know many of them will support caching specific directories between runs

pulumi docker image have just pulumi runtime, but project code like

@pulumi/gcp

is in node_modules.

Interestingly Pulumi's own blog post (https://www.pulumi.com/blog/day-2-kubernetes-migrating-eks-nodegroups-with-zero-downtime/) shows exact problem with current infrastructure as a code tools,but doesn't admit it. No matter what you do, you fall back to bash 😞

Getting the output of a DynamicResource doesn’t seem to work as expected in dynamically typed javascript. I’m setting

myProperty

in the

outs

key of the return value of the provider’s

create

method, but calling

resource.myProperty

returns undefined. Inspecting the resource object itself, I don’t see any values pertaining to

myProperty.

is there a reason why pulumi/pulumi docker doesn't come with all plugins installed? Or maybe having pulumi-full image is something you might be open to?

i think the assumption is that, in addition to the pulumi language packages, you'll be pulling in third-party packages

I'm a little stuck at the moment.

pulumi up

is convinced it needs to finish deleting resources from a previous update on 4 AWS ACM SSL certs. I don't want these resources to be deleted and I can't find any way to tell Pulumi to abort the previous delete attempt

They're all showing up as

completing deletion from previous update

but I'm not seeing any way to modify this using

stack export

@bitter-oil-46081, in https://github.com/pulumi/pulumi/issues/2788 you write

2: For previews and updates where we also plan to run user code, we as the language host if it knows of any plugins that may be needed. Only NodeJS >implements this today, and does so by walking all the package.json's and looking for pulumi specific metadata.

For (2), we now support the language host to communicate an optional server.

how can I change, if possible, package.json so that

pulumi plugin install

pulls plugins from a custom --server?

Just curious, do you (Pulumi folks) see the use of CD tools like Harness or Spinnaker to take over the deployment of applications as complementary? Do you feel that Pulumi can handle those tasks just as well and as such there is no need for those tools? Or are they services you can see Pulumi integrating with?

anybody else having issues with modifying/deleting a launch config from EKS nodes?

consistently get:

error deleting Autoscaling Launch Configuration (monitoring-nodeLaunchConfiguration-1dc3c51): ResourceInUse: Cannot delete launch configuration monitoring-nodeLaunchConfiguration-1dc3c51 because it is attached to AutoScalingGroup monitoring-475ed714-NodeGroup-JKFQB8KKR78N

which means you can’t destroy a cluster

Just wondering if there’s anything we can do to push this issue forwards? https://forums.aws.amazon.com/thread.jspa?threadID=307382

hi all - does anyone have any info on how terraform versions work with Pulumi’s

terraform.state.RemoteStateReference

? I’m just trying it out for the first time, but get a version mismatch:

terraform:state:RemoteStateReference (synchronicity):
    error: Preview failed: error refreshing Terraform state: state snapshot was created by Terraform v0.12.6, which is newer than current v0.12.0; upgrade to Terraform v0.12.6 or greater to work with this state

My installed version of terraform is 0.12.6, so I assume Pulumi is bundling 0.12.0?

Hey folks, is there a way I can set the

policy

on the

RestApi

object when using the

awsx/apigateway.API

approach? I can't see a way of configuring the details beyond what is available on the API object, am I gonna have to use the

aws/apigateway

bits to build this up manually?

Hey guys, with GKE I am setting a cluster stack separately. In the app stack I try to reference using StackReference, on the pulumi platform, both the k8sProvider and kubeconfig are showing as outputs. But if I try to reference these in my app deployment, it does not get located and defaults to kubectls current context. I reference the stack with:

export const clusterStackName = config.require("clusterStackName");
const clusterStack = new pulumi.StackReference(clusterStackName);

The stack name uses <organisation>/<project>/<stack> so: ianbarry/infrastructure/ci as an example. I reference this stack like follows in both service and deployment CustomResourceOptions object:

provider : new k8s.Provider(clusterStackName,{
    kubeconfig: clusterStack.getOutput("kubeconfig")
})