@elegant-rose-64918 you can merge the logic of phase 2 and 3. if you never expect more than 1000 results, you can just do

getRange({ start: 0, end: 1000 })

, and it will return an array with the exact number of the results if you never expect more than 4000 results, you can do

each(result => { /* do something with result */});

and fill an array with the results

In which record is that?

ok - i’ve finally got some time to attempt to “import” an existing deployment as a pulumi stack

despite our previous discussion, it’s not clear how to get started

@big-piano-35669 had suggested trimming some gunk from

pulumi stack export

and then running refresh, but for a new/empty stack, there’s nothing to trim to get urns or anything like that

suggestions?

So I've got a setup where if I refresh it it says it needs to delete and recreate some openstack compute instances, but the diffs are exactly the same no change to urn, id, or anything else. If I ok that refresh my stack state is now buggered and gives an error if I try to do anything with it.

panic: fatal: An assertion has failed goroutine 159 [running]: github.com/pulumi/pulumi/pkg/util/contract.failfast(0xef018d, 0x17) /home/travis/gopath/src/github.com/pulumi/pulumi/pkg/util/contract/failfast.go:23 +0xf3 github.com/pulumi/pulumi/pkg/util/contract.Assert(0x0) /home/travis/gopath/src/github.com/pulumi/pulumi/pkg/util/contract/assert.go:26 +0x49 github.com/pulumi/pulumi/pkg/resource/plugin.(*provider).Read(0xc420946ff0, 0xc42147d170, 0x81, 0x0, 0x0, 0xc42113b770, 0xc420946ff0, 0x1, 0x42ebab, 0xc4210ebed4) /home/travis/gopath/src/github.com/pulumi/pulumi/pkg/resource/plugin/provider_plugin.go:401 +0x5e github.com/pulumi/pulumi/pkg/resource/deploy.(*refreshSourceIterator).newRefreshGoal(0xc42101ca20, 0xc4200e2000, 0x3f, 0x0, 0x0) /home/travis/gopath/src/github.com/pulumi/pulumi/pkg/resource/deploy/source_refresh.go:158 +0x515 github.com/pulumi/pulumi/pkg/resource/deploy.(*refreshSourceIterator).Next(0xc42101ca20, 0x0, 0x0, 0x0, 0x0) /home/travis/gopath/src/github.com/pulumi/pulumi/pkg/resource/deploy/source_refresh.go:129 +0xe6 github.com/pulumi/pulumi/pkg/resource/deploy.(*PlanExecutor).Execute.func2(0xc42028ae10, 0xc421032180) /home/travis/gopath/src/github.com/pulumi/pulumi/pkg/resource/deploy/plan_executor.go:96 +0x4b created by github.com/pulumi/pulumi/pkg/resource/deploy.(*PlanExecutor).Execute /home/travis/gopath/src/github.com/pulumi/pulumi/pkg/resource/deploy/plan_executor.go:94 +0xaf

Can just restore the old stack state that I had saved so I'm not blocked, and I don't need the refresh right now but worried this is gonna bite when I actually need it

But sounds like the whole refresh thing is being rewritten next week? So should I just wait and try again after that's landed?

What should I do when my

pulumi update

visually stopped making any progress and seems idle for hours? Ctrl-C will make me do

refresh

which I have bad experience with...

Can I use Pulumi for my local developer machine and to deploy it on a simple server (without having a cloud stack installed?)

This might be a dumb question but I haven't dove in deeply yet - how does Pulumi, when using JS/TS, interoperate with other modules for the purpose of code reuse? Is there an example out there? (My guess as to implementation is that internally there's a cross-module registry being provided to the module code that's updated when a resource's constructor is called, but I'm still getting my bearings; I just know that for us composable resources is a requirement.)

With one question (awesomely) answered, I had one other implementation question with regards to serverless queues etc - the subscription logic in

aws-js-sqs-slack

is inline in the module. Is there documentation somewhere on how that's packaged to be delivered to Lambda/Cloud Functions/etc? The

package.json

file includes

@slack/client

, so is it just packing the entire Pulumi module definition and shipping it up? (That has some potential implications with regards to secrets, hence the question)

But creating and starting a count are two different things...

So I've got an odd create/refresh issue, and I'm not sure if it's a bug with pulumi or the terraform-openstack-provider. The problem is that openstack.networking.network defines a field called "segments" in it's schema (https://github.com/terraform-providers/terraform-provider-openstack/blob/master/openstack/resource_openstack_networking_network_v2.go#L69). When I create a network with pulumi and don't set this attribute (because it's optional and honestly I'm not actually sure what its for) there is no "segments" field set in the state file, that's because the openstack terraform provider never returns it as an attribute (see the read method, which is used as the return for create as well https://github.com/terraform-providers/terraform-provider-openstack/blob/master/openstack/resource_openstack_networking_network_v2.go#L201). So MAYBE this is a bug on terraform that there's no way to mark an attribute as input only? At any rate if I then call refresh pulumi then ADDS a segments field, it seems because it fills in all default values for inputs (which includes segments) passes that struct to terraform Refresh which calls read to fill in that struct, but it doesn't remove the segments field. So yeh not sure who's really at fault here, but did wonder if providers are prone to doing things like this if pulumi could just not fill in the default fields at all before passing to Refresh?

Hi, I'm trying to install azure+pulumi on a new laptop. Getting "Azure CLI Authorization Profile not found" even after successful CLI login. What else should I check?

Has anyone done a similar thing to the Travis templates for running Pulumi under AWS CodeBuild?

Really nice post from @creamy-potato-29402 on Kubernetes Deployments at https://t.co/SF3petfLxU

What is azure:environment?

error: Missing required configuration variable 'azure:environment'

Is the GitHub app open source? That looks like it has most of the basic bits in it for doing what I want for CodeBuild as an alternative to Travis CI

How can I handle passing a namespace when using the k8s plugin with helm? I don't want me app deployed in

default

.

thanks!

it is possible to start a gke cluster with pulumi gcp and then deploy things to it with pulumi kubernetes all in one go?

It is! We don't have an example, but this has been on our list recently, and I'm spelunking in K8s/GCP right now, so I can see if I can put together an example.

There's an Azure example of this at: https://github.com/pulumi/examples/tree/master/azure-ts-aks-helm

man that's cool

so you just attach the provider in resource options

Exactly right! Only snag I am running into is that the GKE resource (

gcp.container.Cluster

) doesn't appear to export the raw kubeconfig. It's ok, we can easily fake it up, but it's a little messier than the AKS example. (It's also possible I'm missing a simpler way of doing this.) Hopefully will have something working soon.