This message was deleted.

sparse-intern-71089

10/18/2019, 5:27 PM

This message was deleted.

acoustic-toothbrush-71581

10/18/2019, 5:29 PM

deployment: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/kubernetes/apps/v1/#Deployment, status: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/kubernetes/apps/v1/#Deployment

gorgeous-egg-16927

10/18/2019, 6:17 PM

Pulumi automatically waits for k8s resources to be ready, so you shouldn’t have to check the status manually. This thread has an example of depending on resources created as part of a helm chart: https://pulumi-community.slack.com/archives/C84L4E3N1/p1571331362260000

acoustic-toothbrush-71581

10/18/2019, 6:21 PM

@gorgeous-egg-16927 thanks! I give that a whirl. Also do you know is there a better way to debug things like this. Running pulumi up can take a minute or two between changes

gorgeous-egg-16927

10/18/2019, 7:46 PM

I’m not sure I completely understand your question, but I think you might be confused about how to use Input/Output types. https://www.pulumi.com/docs/intro/concepts/programming-model/#outputs should help there. In your specific example, you should be able to do something like:

Copy code

deployment.apply(k => { console.log(Object.getOwnPropertyNames(k)) })

The return value of an

apply

is an Output, but it’s unwrapped/resolved within the function inside of

apply()

5 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.