resources: azure1: type: pulumiprovidersazure-native properties: subscriptionId: ${subscriptionId1} azure2: type: pulumiprovidersazure-native properties: subscriptionId: ${subscriptionId2}

then for a database:

sqlDatabase: type: azuresqlDatabase options: provider: ${azure1} properties: resourceGroupName: ${sqlResourceGroupName} serverName: ${sqlServerName} createMode: Copy elasticPoolName: ${sqlElasticPoolName}

and the containerapp:

containerApp: type: azure-nativeappContainerApp options: provider: ${azure2}

J

Hi Everyone, I'm trying to use the result of a string function in a resource, but it won't let me. Is there a way to do this without creating a variable for each function result then using that in the resource?

ses_DomainIdentityVerification:
    type: aws:ses:DomainIdentityVerification
    properties:
      domain:
        fn::invoke:
          function: str:trimPrefix
          arguments:
            # arguments dictionary
            prefix: "production." # the prefix to trim
            string: "${ses_DomainIdentity.id}" # the string from which to trim it
...
Error: aws:ses/domainIdentityVerification:DomainIdentityVerification is not assignable from {domain: str:index:trimPrefixResult}

Hi Everyone, I cannot get to the bottom of this. A string is being converted to an integer, or something like that - resulting in leading zero being stripped. I've tried double quoting it, single quoting it. Any advice appreciated. my

Pulumi.develop.yaml

file

config:
  aws:profile: 028111111111_AWSAdministratorAccess
  aws:region: ap-southeast-2
  myprojectname:aws_account_id: "028111111111"
  myprojectname:dns_domain: "redacted"
  myprojectname:aws_route53_zoneid: "redacted"

When I attempt to use this value

aws_account_id

in the code, it strips the zero. The stripping doesn't happen to the

aws:profile

. Perhaps because it contains some alpha characters too, or perhaps because the aws provider handles the variable differently. This is where I tried to use it (in an IAM policy)

# Allow to send emails with SES.
            - Action:
                - ses:SendEmail
              Effect: Allow
              Resource: "*" # "arn:aws:ses:${aws:region}:${aws_account_id}:identity/${ses_DomainIdentity.domain}" # can't use this due to bug with yaml stripping leading 0 from aws_account_id

anyone have a work around for using assumeRoles with the yaml runtime? For instance this config doesn’t work

config:
  aws:assumeRole:
    roleArn: xxx
  aws:region: us-east-1

Hello, is there a way to have multiple yaml files for single stack? We'd like to split services by files to not have 1000 lines

Are maps supported for yaml? I'm getting error

* unexpected configuration type 'map[string]interface {}': valid types are string, List<string>, number, List<number>, integer, List<integer>, boolean, List<number>

for

config:
  cloud_run:resources:
    ingress: "all"

Is there any issue with parsing floats from yaml config? In yaml I have value

cloud_run:APP_TRACE_SAMPLING_RATE: "0.001"

but preview its getting 0. I tries to set

0.1

it give 0, tried

"0.1"

also 0 but

"a0.01"

five

a0.01

~ template: {
          ~ spec: {
              ~ containers: [
                  ~ [0]: {
                          ~ envs: [
                              ~ [1]: {
                                      + name : "APP_TRACE_SAMPLING_RATE"
                                      + value: 0
                                    }
                            ]
                        }
                ]
            }
        }

Is there any way to propagate tags to all resources using YAML?

How can I use Stack Reference with YAML (can I?)

Can I use logic and loops in YAML?

Figuring out arrays in YAML was a huge pain in the ass. It wasn't until I found this page, that I discovered what it was expecting: https://www.pulumi.com/docs/intro/concepts/config/#strongly-typed-configuration

config:
  apiAccessKeyWhitelist:
    type: array
    items:
      type: string

The errors weren't super helpful:

Pulumi.yaml': 8 errors occurred:
        * #/config/apiAccessKeyWhitelist: oneOf failed
        * #/config/apiAccessKeyWhitelist: expected string, but got object
        * #/config/apiAccessKeyWhitelist: expected integer, but got object
        * #/config/apiAccessKeyWhitelist: expected boolean, but got object
        * #/config/apiAccessKeyWhitelist: expected array, but got object
        * #/config/apiAccessKeyWhitelist: doesn't validate with '/$defs/configTypeDeclaration'
        * #/config/apiAccessKeyWhitelist/items: doesn't validate with '/$defs/configItemsType'
        * #/config/apiAccessKeyWhitelist/items: expected object, but got string

Another issue:

We failed to locate the entry point for your program:

Here's what we think went wrong:
      * Your program looks like it has a build script associated with it ('DESTFOLDER=dist/lambda-layer/nodejs && mkdir -p ${DESTFOLDER} && cp package.json package-lock.json ${DESTFOLDER} && npm install --prefix ${DESTFOLDER} --production --ignore-scripts && rm ${DESTFOLDER}/package.json ${DESTFOLDER}/package-lock.json && nest build').

but it is built...

ls dist/app |wc -l
      15

What the heck, can I disable this implicit behavior? https://github.com/pulumi/pulumi/pull/1460/files#diff-068223f4c0480deece94249ad4391ea526a6ddb84b483f847059632096ba2c55R116

ahh, the runtime in my YAML was

nodejs

still... but now I have the array issue again

Does anyone have working examples of arrays and stack references? The examples I've tried from the docs aren't working

Anyone?

I got past the StackReference issue. My major blocker now is the array from configuration. Why is this so terrible?

This seems to successfully get the vpc, but how do make it a local resource?

variables:
 vpc:
    fn::invoke:
      function: aws:ec2/getVpc:getVpc
      arguments:
        id: ${vpcId}

This does not work

shared-vpc:
    get: ${vpc}

Okay, that might be a bug with the interpolation. If I hardcode the vpcId, then it works.

Is there any way to propagate tags to all resources using YAML?

Currently no. There's no support for stack transforms, we've been thinking about maybe enabling that via an external policy but might also be worth supporting some simple transforms in yaml directly so feel free to raise a request.

How can I use Stack Reference with YAML

Yes, the code you posted to the thread looks right to me but it does look like the docs pages is missing a section. Raised an issue for that https://github.com/pulumi/pulumi-hugo/issues/2798

Can I use logic and loops in YAML?

No the design is intended to be for very simple uses cases, our thinking is if you need logic and loops you shouldn't be using YAML. There is an issue for this https://github.com/pulumi/pulumi-yaml/issues/191 but the current stand is either upgrade to a full language (which is what

pulumi convert

helps with) or use a templating system like CUE or Jinja.

Figuring out arrays in YAML was a huge pain in the ass.

Structured config like arrays and objects is still being improved. As you've pointed out the errors aren't great because it's pretty much a raw dump of the schema validation, we have an issue tracking that at https://github.com/pulumi/pulumi/issues/11129.

My major blocker now is the array from configuration. Why is this so terrible?

I think (and I haven't touched the yaml codebase for a bit) because yaml never had support for arrays or objects as config. The engine can handle them but YAML doesn't. I'm working on a new set of tests to cover all the language to makes sure they're consistent about their support for config values. Fixing this should fall out from that work.

This seems to successfully get the vpc, but how do make it a local resource?

Not totally sure what your asking here given the code snippet? Do you mean how do you define a vpc resource for pulumi to create instead of get?

Any plans to fix this issues? https://github.com/pulumi/pulumi-yaml/issues/452 https://github.com/pulumi/pulumi-yaml/issues/453

I wonder if it's possible to find the IP address of an ECS container? I'm using Crosswalk awsx to create the ECS, ECR, LB, etc. But my app in the container is complaining about the LB healthchecks because the LB is contacting the container on its local IP, which is not in the

ALLOWED_HOSTS

of my app. Therefore the LB thinks the target is unhealthy and pulumi times out

I wonder how I can access the security group object which is created as an underlying resource of the awsx FargateService? I want to create a security group which can be attached to the DB that my fargateservice containers are connecting to.

sg_allowPostGresFromECS:
    type: aws:ec2:SecurityGroup
    properties:
      description: Pulumi managed. Allow Postgres inbound traffic from ECS.
      ingress:
        - description: Postgres from ECS.
          fromPort: 0
          toPort: 5432
          protocol: tcp
          securityGroups:
            - ${???????}
      egress:
        - fromPort: 0
          toPort: 0
          protocol: "-1"
          cidrBlocks:
            - 0.0.0.0/0

I notice that the yaml example section of Providers in the docs is missing - does this mean it is not possible to create multiple aws:Providers (e.g. for different regions, or different aws accounts), and use them in a Pulumi.yaml file?