Trying to access the

principalId

from the

identity

property of API Management service:

export const dump = service.identity.principalId

However, it seems that accessing properties of

identity

is not doable for some reason:

error TS2339: Property 'principalId' does not exist on type 'Output<ServiceIdentity | undefined>'.

Property 'principalId' does not exist on type 'OutputInstance<ServiceIdentity | undefined> & LiftedObject<undefined, never>'.

But the outputs of apimanagement say it should be possible

interface ServiceIdentity {
        /**
         * The Principal ID associated with this Managed Service Identity.
         */
        principalId: string;
        /**
         * The Tenant ID associated with this Managed Service Identity.
         */
        tenantId: string;
        type: string;
    }

Am I missing anything? …. Forgot to mention that outputting the

identity

object works as expected

~ dump: {
      + dump: {
          + principalId: "9f9e1f60-933e-49b5-b6a3-7c416e2b542a"
          + tenantId   : "152e4c75-3657-4284-bb2c-0d825873d72b"
          + type       : "SystemAssigned"
        }
    }

Try

service.identity.apply(id => id && id.principalId);

The fact that

identity

is not always there (

| undefined

) makes it a bit harder to use.

and any particular reason that’s not always there?

You don't have to configure identity for the API management

hi everyone, can anybody point me an example how to set up logs in Azure App service ?

azure.appservice.AppService

Hello All, I am new to Pulumi and TypeScript. I've been trying to extend the example at...https://www.pulumi.com/blog/get-started-with-docker-on-aws-fargate-using-pulumi/ to include a statsd sidecar. I am currently stuck trying to define the containerPorts. I've tried the following:

const statsdPortProtocol: aws.ecs.Protocol = 'udp';
const statsdAdminPortProtocol: aws.ecs.Protocol = 'tcp';
const statsdPort = { port: 8125, protocol: statsdPortProtocol };
const statsdAdminPort = { port: 8126, protocol: statsdAdminPortProtocol };

and used it as

portMappings: [statsdPort, statsdAdminPort]

but I am getting the error:

Invalid 'containerPort' setting for container 'statsd'.

Hi, how do I enable CORS on per method basis for AWS API gateway?

Anyone that have links or information regarding moving Digitalocean infrastructure from Terraform to Pulumi? It's not very big and most things was taken care of by tf2pulumi and then some manual edits to add in

{import:"resource id"}

. Problem is that some resources give warnings like the following, while the inputs are configured exactly the same as previous TF code and is correct in relation to the existing TF state. 🤔 And if I run

terraform plan

there are no changes to be made, so there should not be any wild configuration changes floating around.

digitalocean:index:Droplet (mgr):
    warning: inputs to import do not match the existing resource; importing this resource will fail

How do you reference a NodeJS module in a Git subdirectory with

npm

? The only solution I’ve found so far seems to be switching to

yarn

at all. (see https://github.com/npm/npm/issues/2974 -> https://npm.community/t/allow-installing-packages-from-git-subdirectories/3973)

I am very new to TypeScript so I'm hoping this is an easy question for someone else. I have a functional loop that is creating/importing our IAM groups from a text file: const groupsList = (fs.readFileSync('groups.txt')).toString().split('\n') let groups = []; for (let group in groupsList) { groups.push(new aws.iam.Group(groupsList[group], {name: groupsList[group]}, {import: groupsList[group]})); } export let groupNames = groups.map(s => s.name); Later on, I want to re-use the created groups in a aws.iam.GroupPolicyAttachment resource: const groupPolicyAttachment = new aws.iam.GroupPolicyAttachment("testGroupoAttachment", { group: (<groupType export goes here>})), policyArn: testPolicy.arn }); The groupPolicyAttachment doesn't accept a string value for group attribute. I'm trying to figure out how to get the original groupType from the original loop. The current export was just a test, but again, I end up with a string value.

set the channel topic: All TypeScript all the time! Noob friendly - there are no dumb questions.

Trying to upload docker image to a repo...

// import { Repository, RepositoryImage } from "@pulumi/awsx/ecr";

export function createImage() : RepositoryImage {
  const repository = new Repository("myrepo");
  const repImage = repository.buildAndPushImage("./Application");

  return repImage
}

and I get this error on the return line

error TS2739: Type 'OutputInstance<string> & LiftedObject<String, number | "length">' is missing the following properties from type 'RepositoryImage': repository, imageValue, image, environment

. If I change

createImage() : RepositoryImage

to any I get a string error...whats going on here?

I have 0.18.13 for the awsx library, https://github.com/pulumi/pulumi-awsx/blob/v0.18.13/nodejs/awsx/ecr/repository.ts#L70 indicates that's the right type...

Typescript question: How can I append an additional field & value to an existing variable of type

pulumi.ComponentResourceOptions

? I want to add

dependsOn

to a

kubernetesOptions

variable defined beforehand.

Is it possible to set

import:

for resources in a

helm.v2.Chart()

as well? (See https://www.pulumi.com/blog/adopting-existing-cloud-resources-into-pulumi/) Maybe via

transformations

?

links aren't supported with fargate so how can i do depends on ? trying to get nignx container to connect to php container

const appService = new awsx.ecs.FargateService("app-svc2", {
    cluster,
    taskDefinitionArgs: {
        containers: {
            php: {
                image: img,
                cpu: 102 /*10% of 1024*/,
                memory: 50 /*MB*/,
                essential: true
            },
            nginx: {
                image: nginx,
                cpu: 102 /*10% of 1024*/,
                memory: 50 /*MB*/,
                portMappings: [web],
                essential: true,
                
            },
        }
    },
    desiredCount: 2
});

Best practice on handling

pulumi.Output

when using helper functions that want unboxed values (and especially reusing the result for a new pulumi resource name)

Is there a quick way to generate and view the package that would be deployed for a given lambda? Trying to diagnose some node module packaging issues, but don’t want to deploy to an actual environment to be able to view the compiled code

@happy-parrot-60128 would

pulumi preview

do that for you?

I knew we can do stack reference in the same aws account like this:

import * as pulumi from "@pulumi/pulumi";
const current_stack = pulumi.getStack(); // assume current_stack deployed into account A
const infra_stack = new pulumi.StackReference(`acmecorp/infra/${current_stack}`);  // assume infra_stack also deployed into account A

But is there a way to do stackreference across aws accounts ?

import * as pulumi from "@pulumi/pulumi";
const current_stack = pulumi.getStack();  // assume current_stack deployed into account A
const infra_stack = new pulumi.StackReference(`acmecorp/infra/${current_stack}`); // assume infra_stack deployed into account B, does this really work ?

Thanks.

is there a way to set the package manager used by the pulumi cli? I prefer to use

pnpm

rather than

npm

or ``yarn``

Does Pulumi support something like config flattening, such that you could have something like

base.yaml

that

pulumi.dev.yaml

, and

pulumi.staging.yaml

can share some common values from the base?

Is there a template repo or something I can clone so I can quickly reproduce a bug? That is, what's the shortest path to working typescript/aws code that demonstrates (what I htink) is a bug?

I think it's impossible to, in one deployment, create an SSL certificate and DNS entries to validate that certificate for a domain with multiple "subjectAlternativeNames" in a general way.

anyone about to answer a noob question in #general ? Probably should have put it in here

has something changed with

ComponentResourceOptions

? i'm getting

index.ts(29,47): error TS2322: Type 'Provider' is not assignable to type 'ProviderResource'.
      Types of property 'id' are incompatible.

when trying to

const k8sProvider = new k8s.Provider(`cointainers-${environment}`, {
        kubeconfig: fs.readFileSync(`.circleci/${environment}.json`).toString()
    })

const t = new test({provider: k8sProvider}) // <---- pass provider as options to class which extends pulumi.ComponentResource

class test extends pulumi.ComponentResource {
    constructor(opts?: pulumi.ComponentResourceOptions) {
        super('test', "test", {}, opts)
    }
}

I am experimenting with using

pulumi.ComponentResource

to build in some validation logic. What I am seeing is that if I throw a

pulumi.ResourceError

pulumi prints it twice with a stack trace. It appears that pulumi.ResourceError ignores my “hideStack = true” parameter. It also appears that apply occurs before or regardless of an error creating the output. I’m probably doing something wrong here, but I would like to have a single nice error displayed w/o the stack and only perform validation if the underlying resource create succeeds.

It appears that if any error is thrown inside of an apply() the error will be printed twice for the stack + the error itself.