resulting in

"apiVersion: v1\nkind: List\nitems:\n\n"

I'm new to Pulumi as well, but yes, it looks like it's a result of the async behavior. Any reason you can't pull up the code from results.map inside that apply() clause?

because it’s really hard to do that

Getting at generated values in Pulumi can be really tricky. @white-balloon-205 pointed out that with some refactoring, it's possible to write code that doesn't rely on the apply clauses at all.

I can’t get either interpreted or interpolated values in the above snippet to work

¯\_(ツ)_/¯

@white-balloon-205, could you please review my snippet?

What about something like this?

import * as aws from "@pulumi/aws";
import * as pulumi from "@pulumi/pulumi";


export function generateMachinesYaml(
    masters: aws.ec2.Instance[],
    workers: aws.ec2.Instance[]
) {
    let results: any[] = [];
    for (let i = 0; i < masters.length; i++) {
        const m = masters[i];
        pulumi
            .all([m.id, m.publicIp, m.privateIp])
            .apply(([id, publicIp, privateIp]) =>
                results.push({
                    id,
                    publicIp,
                    privateIp,
                    label: "master"
                })
            );
    }
    let listItems: string[] = [];
    for (let i = 0; i < workers.length; i++) {
        const m = workers[i];
        pulumi
            .all([m.id, m.publicIp, m.privateIp])
            .apply(([id, publicIp, privateIp]) =>
                listItems.push(
                    `- apiVersion: <http://cluster.k8s.io/v1alpha1|cluster.k8s.io/v1alpha1>
  kind: Machine
  metadata:
    name: $id}
    namespace: weavek8sops
    labels:
      set: "worker"
  spec:
    versions:
      kubelet: 1.14.1
      controlPlane: 1.14.1
    providerSpec:
      value:
        apiVersion: baremetalproviderspec/v1alpha1
        kind: BareMetalMachineProviderSpec
        public:
          address: ${publicIp}
          port: 22
        private:
          address: ${privateIp}
          port: 22`
                ))
            .apply(() => {
                // listItems = listItems.join("\n");
                const yaml =
                    `apiVersion: v1
kind: List
items: ${listItems}`;
                return yaml;
            });
    }
}

I have an aws / ts stack that I last updated a month ago and now it wants to do delete a bunch of my role attachments. Was anything changed that might've caused this? I have a decent amount of .apply / .then programming going on so I'm wondering if something changed in a way which makes that invalid...

@billowy-laptop-45963 the preview mode should give you an idea what's going to be changed. That can lead you towards the section where the code may have changed.

Because resources can complete at different times, order isn't guaranteed, and that can cause changes (such as the same routes now being applied in a different order).

Is there a way to have the

pulumi

CLI tool not check for and report on newer versions?

What is the best way to refactor code where some resource name change?

Also, how do I find the URN of resources. Some resources don’t show the URN in the Pulumi console.

@white-balloon-205 please check your inbox, thank you.

Hi Pulumi team. Are you aware that examples have disappeared on documentation (at least for typescript/azure) since this commit : https://github.com/pulumi/docs/commit/7b515e0bd6c50d55102634ccf043634f1622c8a3#diff-78672af2fbbf340a6926b7629ea1627d ?

Hi guys ! I have a cluster deployed on Azure (Aks) vía Pulumi , but for some reason Pulumi keeps applying the configuration without any ‘Pulumi up’ action trigger. Do you have an idea what is happening? Check the image , this just happened out of nothing :(

Yay, terraform recently implemented a long awaited feature “Add desired_status argument to google_compute_instance” (https://github.com/terraform-providers/terraform-provider-google/pull/5734). Which means you can create instances in a TERMINATED state (since you don’t pay for them then). What’s the process of bumping pulumi-gcp? Is that something I should make a PR for, happens on a timed schedule?

@thousands-london-78260 When it’s in a release it will get brought over

@broad-dog-22463 manages much of that, but it shouldn’t be too long following a release upstream

i'm using IAM STS temp credentials to run pulumi from my laptop. how would i run it in a gitlab job? i've tried setting up an access/secret key but it just tells me that it's invalid creds

do i have to

pulumi config set

? i'm just using the standard env vars right now

i figured pulumi would read them

Is there a doc on organizing your pulumi code? I am playing with the Auth0 sample and the API gateway sample (typescript) and am unsure if I should merge them into one big index.js or if there is a modular approach to applying them to the same stack.

is there any way to get properties of the provider being used? E.g. Determining if the AWS provider is using a

profile

or an assumed

role_arn

We’re publishing abstracted AWS/K8S providers for our software devs and using env vars or depending on the pulumi config isn’t viable because a user may be using an explicitly created provider in their IaC

hi, is there any workaround for https://github.com/pulumi/pulumi-aws/issues/814? It''s a real blocker for me. I can't deploy one of required Stacks (others stacks are deployed well).

Hello, I am getting started with an organization and a naive run of

pulumi new

creates a project and stack in my personal account rather than the org. I cannot find a switch or env var to instruct pulumi to use the org as the default account. Is this possible? Thanks!

Quick security question about key management practices: So far my keys for GitHub actions deploys into AWS accounts/environments have just been manually added to GitHub Secrets and used as environment variables for Pulumi's action to deploy with. It occurred to me that it would be possible to store those secrets as Pulumi config secrets. Is that considered a safe approach?

Can I rename a Pulumi project? If so, what are the steps to do it?

How does Pulumi Terraform Bridge deal with default values configured in a resource? I am running into an issue i.e. a resource is defined as this:

"list_policy": {
		(...)
				"allow": {
					(...)
							"all": {
								Type:         schema.TypeBool,
								Optional:     true,
############ --->		    	Default:      false,                 <-- Default Value #########
								ExactlyOneOf: []string{"list_policy.0.allow.0.all", "list_policy.0.allow.0.values"},
							},
							"values": {
								Type:         schema.TypeSet,
								Optional:     true,
								ExactlyOneOf: []string{"list_policy.0.allow.0.all", "list_policy.0.allow.0.values"},
								Elem:         &schema.Schema{Type: schema.TypeString},
								Set:          schema.HashString,
							},
						},
					},
				},

https://github.com/terraform-providers/terraform-provider-google/blob/1f9e0cb9c3cef1c65cfd2054ca8dfd2795ac42a6/google/resource_google_organization_policy.go#L55 And I created it like this:

new projects.OrganizationPolicy('Only allow resource in Europe', {
    constraint: 'gcp.resourceLocations',
    project: gcloud.project,
    listPolicy: {
        allow: {
            values: ['in:europe-west4-locations']
        }
    }
})

What would be the value of

resource.listPolicy.allow.all

?