Hello, Today, I’m able to publish pulumi component in a private npm repository in order to reuse them in several pulumi projects, and it works like a charm (thanks pulumi team). As the component are in typescript, we can only reuse them in pulumi typescript project. In a big organisation, we would be able to let some team works in other languages like python. Is there a way to share component for a multi-language use ? May be by generating them ?

I am trying to re-parent a resource into a custom component. The old parent is the stack (which is the implicit root). On my resource, which is now inside the

pulumi.ComponentResource

subclass, I add these custom resource options:

parent: this,
aliases: [{ parent: pulumi.getStack() }]

However, I still see a

create

and

delete

as separate lines in my Pulumi preview. How can I make this work?

Hi, What is the expected behavior of an

pulumi.config.require_object("config")

if the

config

object has data that was deemed a secret. I am trying to understand if

require_object

automatically translates the portion of the object into a secret that was set by using pulumi config set --secret. FWIW it seems to mask the secret in pulumi preview, but when writing the state file it seems to be showing keys in plain text.

@early-intern-90238 please check your inbox

👋 hi all

I’m banging my head against the wall.. I’m trying to get value interpolation working but nothing seems to work… I read the https://www.pulumi.com/docs/intro/concepts/programming-model/ a bunch of times… and I still don’t understand why I can’t get values showing up. I tried using

.all().apply()

,

.output()

,

.interpolate()

, … idk what to do..

@ripe-lighter-13633 try putting the "push" inside the apply() clause. Make your mToPush just a variable and ignore the return of .all(). Either that, or you may need to "return" a value from the apply().

I had that previously and it still didn’t work

I edited my message. Not sure if you saw the update?

after putting .push() inside apply, I get an empty results

probably because it’s all happening async

Can you paste in that revised snippet?

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 ?