Anyone having issues setting up an aks cluster in azure? I manually created a service principal for pulumi to run as, it's got all the permissions i can find but i get this when i try to create a new SP with pulumi

SP creating error: Plan apply failed: graphrbac.ApplicationsClient#Create: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="Unknown" Message="Unknown service error" Details=[{"odata.error":{"code":"Authorization_RequestDenied","date":"2019-05-07T14:22:29","message":{"lang":"en","value":"Insufficient privileges to complete the operation."},"requestId":"6df1d82f-17bb-48da-94d7-8dd03e6a39fa"}}]

Is there a roadmap that the pulumi team can share?

are there are docs/how-tos out there on using lambda@edge with pulumi?

Hi all, I'm using Pulumi via JavaScript with AWS and seeing some strange behavior with the

getAmi

function. (I freely admit this could be due to my lack of experience with JavaScript.) Here's the code in question:

const bionicAmi  = aws.getAmi({
    filter: [
        { name: "name", values: "ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server*" },
        { name: "virtualization-type", values: "hvm" },
        { name: "root-device-type", values: "ebs" },
    ],
    mostRecent: true,
    owners: [ "099720109477" ],
});

Using this set of filters with the AWS CLI works perfectly, but here it returns a completely different AMI. What am I missing?

One simple possibility is a difference in region?

I have the AWS_REGION environment variable set, does Pulumi not honor that?

(The correct region is also set in my AWS CLI profile configuration.)

The issue with my

getAmi

function above was a typo. It's

filters

, not

filter

. Argh.

I'm doing a

pulumi up

and it's bombing out with this error. Any ideas what's going on and how to fix this?

weird

I have a cloud.API created with cloud-aws that is returning content in base64 encoding no matter what I try to do

I have a cloudfront distribution but it shouldn’t be in front of this api gateway…

unless it is somehow

bizarre

Is it a bug that when I get

azure:storage:Blob (vmshutdownpolicystorageblob):
    error: Plan apply failed: Error creating storage blob on Azure: Error opening source file for upload "./functions/build/functionapp.zip": open ./functions/build/functionapp.zip: no such file or directory

that pulumi still uploads a file with size 0?

Is there a way to specify roles and policies of the lambdas in awsx API? Or are they locked down to the default full access roles?

Hi, I have two questions on best practices when using Pulumi: 1. What is the best way to create global resources that are shared between Stacks (dev, stage, live)? E.g. I want to setup a Container Registry with a cloud provider and use it in all stacks. Do I have to create a project for the shared components? 2. Since outputs are persisted in the Pulumi Cloud, is it possible to have the outputs encrypted when they contain generated secrets (when using

RandomString

from

@pulumi/random

)? Or do I have to forbear to do that and instead generate all secrets beforehand and add them to the config with

pulumi config --secret  set ...

?

i've put shared components in a different project then i export the parameters used to create the resources as a private npm package so that dependent layers can import and retrieve them

when i try to

pulumi login --local

I get the following error :

error: problem logging in: unable to open bucket file://C:%!C(MISSING)Users%!C(MISSING)username: open blob.Bucket: parse file://C:%!C(MISSING)Users%!C(MISSING)username: invalid URL escape "%!C(MISSING)"

i believe it's WIP i've downgraded to 0.17.8 in the meantime

cant get any local login to work

are you saying I should downgrade to 0.17.8?

Follow-up: can anyone shed light on why a cloud-aws api would be returning base64-encoded strings no matter how I do the response? I have working cloud-aws apis on another account and they seem to work fine. I can’t find any differences between the base64 and regular ones code-wise or setup-wise EXCEPT for the one that works had its

binaryMediaTypes

apigateway setting set to

*/*

. I tried adding that to the base64 one but it didn’t start working, and pulumi removes the setting when I

pulumi up

.

Just a comment - I think the permissions model should allow non WRITE users to run previews

makes pre-testing or local dev a bit problematic for things you think may be an issue

Looks like 0.17.10 never made it to https://pulumi.io/latest-version still and the powershell script doesn't appear to support specifying the version like the sh

How do I disable this message from each CLI execution?

warning: A new version of Pulumi is available. To upgrade from version '0.17.9' to '0.17.10', run
   $ curl -sSL <https://get.pulumi.com> | sh
or visit <https://pulumi.io/install> for manual instructions and release notes.

interesting error:

error: gcp:container/cluster:Cluster resource 'alpha' has a problem: : invalid or unknown key: location

I was getting constant nagging about how

region

was being deprecated. So I went through and changed the

region

code to use

location

.