This message was deleted.

sparse-intern-71089

10/02/2019, 5:02 PM

This message was deleted.

cool-egg-852

10/02/2019, 5:17 PM

Also how do we use it if we install from master?

worried-city-86458

10/02/2019, 5:31 PM

I had to switch to

yarn

instead of

npm

then update

packages.json

to refer to

alpha

versions; e.g. for

@pulumi/pulumi

package:

Copy code

{
  "name": "aws-typescript",
  "devDependencies": {
    "@types/node": "^8.0.0"
  },
  "dependencies": {
    "@pulumi/kubernetes": "^1.0.0",
    "@pulumi/pulumi": "^1.3.0-alpha",
    "@types/nodecredstash": "^2.0.0",
    "nodecredstash": "^2.0.2"
  },
  "resolutions": {
    "**/@pulumi/pulumi": "^1.3.0-alpha"
  }
}

I'm sure it would be the same for

@pulumi/kubernetes

cool-egg-852

10/02/2019, 5:31 PM

We use yarn ourselves too.

cool-egg-852

10/02/2019, 5:32 PM

Thanks for the info, I was using

@dev

but

^1.2.0-alpha

looks like it should work too

cool-egg-852

10/02/2019, 5:32 PM

Now I just need to understand how to use this feature

cool-egg-852

10/02/2019, 5:32 PM

Unfortunately the PR https://github.com/pulumi/pulumi-kubernetes/pull/633 did not provide detaisl on it

worried-city-86458

10/02/2019, 5:32 PM

Yeah I couldn't get

@dev

to work with yarn resolutions

cool-egg-852

10/02/2019, 5:33 PM

@gorgeous-egg-16927 Since you wrote the code, maybe you can assist. I am also confused as to how to configure how long Pulumi waits for the job to complete.

creamy-potato-29402

10/02/2019, 5:36 PM

@cool-egg-852 @worried-city-86458 we’ll probably release tomorrow, I’m guessing?

creamy-potato-29402

10/02/2019, 5:36 PM

@gorgeous-egg-16927 is out until tomorrow

cool-egg-852

10/02/2019, 5:36 PM

cool-egg-852

10/02/2019, 5:36 PM

Do you have any idea how to make use of the change?

creamy-potato-29402

10/02/2019, 5:37 PM

Job

creamy-potato-29402

10/02/2019, 5:37 PM

it should work just like any other resource.

creamy-potato-29402

10/02/2019, 5:37 PM

new Job

will cause a “normal” experience where we wait for it to complete, as we do with stuff like

Deployment

cool-egg-852

10/02/2019, 5:38 PM

Gotcha. I wasn’t sure if that’s what the feature did or not.

cool-egg-852

10/02/2019, 5:38 PM

So how do we customize the timeout? For example, I have Job1 and I want it to wait up to an hour for it to complete. Given that

creating

a job only takes a few seconds, I’m not sure if the

create

customTimeouts

is considered as part of this await logic.

creamy-potato-29402

10/02/2019, 5:39 PM

it works the same as customizing any other timeout

creamy-potato-29402

10/02/2019, 5:39 PM

but we will actually wait for the job to complete by default

cool-egg-852

10/02/2019, 5:39 PM

create

now takes into consideration the completion of the job, not just how long it takes to create?

cool-egg-852

10/02/2019, 5:39 PM

I’m referring to

customTimeouts: {create: ''}

creamy-potato-29402

10/02/2019, 5:40 PM

yeah

cool-egg-852

10/02/2019, 5:40 PM

Ok cool. I don’t have an easy way to test this out, which is why I was asking.

creamy-potato-29402

10/02/2019, 5:40 PM

Yeah, I think you can, you can

skip-await

too

creamy-potato-29402

10/02/2019, 5:40 PM

if you put in

dev

in package.json it should “just work”

cool-egg-852

10/02/2019, 5:41 PM

I used

^1.2.0-alpha

and it worked just fine. Thanks for all the assistance.

creamy-potato-29402

10/02/2019, 5:41 PM

creamy-potato-29402

10/02/2019, 5:41 PM

#itsmyjob

cool-egg-852

10/02/2019, 5:41 PM

I understand that documentation is automatically done, I think the problem here was the lack of documentation for anyone who knew how it worked prior to the PR.

creamy-potato-29402

10/02/2019, 5:41 PM

Job

, if you’ll permit my one dad joke for the day

cool-egg-852

10/02/2019, 5:42 PM

I think having documentation for those scenarios is a must.

cool-egg-852

10/02/2019, 5:42 PM

LOL

creamy-potato-29402

10/02/2019, 5:42 PM

you mean, for the await logic?

cool-egg-852

10/02/2019, 5:42 PM

For anytime something is done different than previously.

creamy-potato-29402

10/02/2019, 5:42 PM

the hope was that if we added support the experience would simply get better

cool-egg-852

10/02/2019, 5:42 PM

In this case yes, the await logic.

creamy-potato-29402

10/02/2019, 5:42 PM

I’m guessing we’ll write a blog post about it

cool-egg-852

10/02/2019, 5:43 PM

Because anyone who knew how it worked before will be confused as I was.

cool-egg-852

10/02/2019, 5:43 PM

As the PR mentions 0 ways in how to use the new feature

creamy-potato-29402

10/02/2019, 6:01 PM

The PR is scoped mainly to implementation

creamy-potato-29402

10/02/2019, 6:01 PM

You are right we should communicate this stuff better

creamy-potato-29402

10/02/2019, 6:01 PM

maybe PR is the right place

cool-egg-852

10/02/2019, 6:03 PM

Given it’s linked to in the CHANGELOG.md file, it’s where I would expect some information.

creamy-potato-29402

10/02/2019, 6:09 PM

makes sense

creamy-potato-29402

10/02/2019, 6:09 PM

thanks for the feedback, and cc @gorgeous-egg-16927

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.