Hello, does anyone know how to convert

Output<String>

to

string

? for example

const eksClusterName = eksInfra.requireOutput("eksClusterName"); // This line returns Output<string>
pulumi.log.debug(eksClusterName) // How to let this line work?

Looks like EKS just introduced managed worker groups. How long until Pulumi supports this feature?

Takes a good long time for cloudfront distro's to finish updating, but pulumi up wants to wait for it. Is that the expected behavior?

Is there a way to get the current stack from the pulumi command quickly? The only one I know of is to 'pulumi stack ls' and get the one with the asterisk. I can also find the appropriate file in ~/.pulumi/workspaces/<dir>-<id>-workspace.json. But I'd prefer to use the command.

I'd like to include the current stack in my prompt.

I have a Kubernetes deployment with three replicas where one is leader and the other two are standby. The way this software works, the two standby pods never report as Ready; only the leader pod does. This is desirable, because this Deployment is fronted by a Service, and having the non-leader pods not report as Ready keeps them out of rotation in the Service load balancer. Is there a way to tell Pulumi, "this deployment is ready when one of the three pods is Ready?"

What is people's recommendation when moving from a large terraform base to pulumi? tf2pulumi is lacking tf 0.12 support, so I can't test its quality of output. I suspect it's going to be a rewrite from scratch?

Does Pulumi re-read your program between the preview and update steps?

If I have deleted an EKS cluster from the console, how do I get Pulumi to understand it has been deleted and to figure out what to do with all the deployments. Currently every deployment I have now fails to delete with this message:

error: unable to load schema information from the API server: Get <https://F7E1844F423B2899F4D9B934F2EFE568.yl4.us-west-2.eks.amazonaws.com/openapi/v2?timeout=32s>: dial tcp: lookup <http://F7E1844F423B2899F4D9B934F2EFE568.yl4.us-west-2.eks.amazonaws.com|F7E1844F423B2899F4D9B934F2EFE568.yl4.us-west-2.eks.amazonaws.com>: no such host

I would honestly be fine with destroying the whole stack but that can't be done because I can't get past this error.

Why does this command fail when the urn exists in my stack's state file?

pulumi state delete urn:pulumi:dev::vm-scaler::kubernetes:<http://helm.sh/v2:Chart$kubernetes:rbac.authorization.k8s.io/v1:ClusterRoleBinding::dd-agent-datadog|helm.sh/v2:Chart$kubernetes:rbac.authorization.k8s.io/v1:ClusterRoleBinding::dd-agent-datadog>
 warning: This command will edit your stack's state directly. Confirm? Yes
error: No such resource "urn:pulumi:dev::vm-scaler::kubernetes:<http://helm.sh/v2:Chart:rbac.authorization.k8s.io/v1:ClusterRoleBinding::dd-agent-datadog|helm.sh/v2:Chart:rbac.authorization.k8s.io/v1:ClusterRoleBinding::dd-agent-datadog>" exists in the current state

If I search for

urn:pulumi:dev::vm-scaler::kubernetes:<http://helm.sh/v2:chart:rbac.authorization.k8s.io/v1:ClusterRoleBinding::dd-agent-datadog|helm.sh/v2:chart:rbac.authorization.k8s.io/v1:ClusterRoleBinding::dd-agent-datadog>

in my stack's json file, I will find it.

Is there a way to just delete resources from the pulumi state? Going through a deleting every dependent URN a resource may create is incredibly tedious.

Hey! Could you take a look at https://github.com/avolkov-dev/pulumi-mount-issue ? i'm getting weird error (

VolumeInUse

) when reaattaching existed volume to new instance

I am planning to deploy dev and prod stacks to separate aws accounts. The environments will also have separate stacks. What would be the best way to enforce that dev stacks (there could be many of these) go to the dev account and that the prod stack (of which there should be at most one) goes to the prod aws account? The only thing I can think of is using policy packs. In terraform you would achieve this by having separate provider files for example. Is anybody else doing this in a better way? Or am I wrong in the entire approach?

Hi! It was great seeing the team at Kubecon. Speaking of, I’m curious what thoughts anyone has around where pulumi fits in with kubernetes operators. Will pulumi just be a tool for applying the initial resources of the operator itself, and the corresponding CRDs, or does pulumi potentially have a place in building operators themselves?

hey everyone, I've got a question about turning outputs into concrete values (I think)

I'm trying to get secrets into a fargate container definition

the pulumi.aws.Secret type has name and valueFrom (ARN), both strings

I've got outputs from the parameter store secrets I've created that I would like to pass in

but since valueFrom is a string and doesn't accept an output, I'm not sure how to construct the config so it works

abbreviated config:

const parameter = new aws.ssm.Parameter("SECRET", {
    type: "SecureString",
    value: config.requireSecret("myPulumiSecret"),
});

const service = new awsx.ecs.FargateService("service", {
    cluster,
    desiredCount: 2,
    taskDefinitionArgs: {
        container: {
            secrets: [{
                name: parameter.name,
                valueFrom: parameter.arn, // FAILS, Type 'Output<string>' is not assignable to type 'string'.
            }],
        },
    }
});

I also tried the pattern shown here (https://stackoverflow.com/questions/58341593/pulumi-how-to-serialize-outputstring-to-json/58347396#58347396) with no luck

We use cloud backed storage (s3) instead of pulumi.com, can we still use

pulumi.StackReference

?

Hi all 👋 when you replace a DynamoDB table (for example when the hashkey attribute changes), will the data be deleted?

Hi all, I moved around the local directory in which our pulumi stack was configured, and this has somehow messed up the state management, despite us using a remote stack backend in a Google Cloud Storage bucket. Running any pulumi command now gives the error

Could not get signed url for stack location

. Pulumi version installed on my mac is v1.6.1 Has anybody encountered such an error before or could give pointers towards recovering from this error? I'm willing to download the state file from the storage bucket and restore the state manually, but can't find any clear directions on how to do so, thanks.

pulumi login --cloud-url <gs://xxx-yyy-zzz>
Logged into Agrim-Macbook-Pro.local as agrim (<gs://xxx-yyy-zzz>)

pulumi refresh
Enter your passphrase to unlock config/secrets
    (set PULUMI_CONFIG_PASSPHRASE to remember):
Previewing refresh (experiments):


Resources:

Do you want to perform this refresh?
No resources will be modified as part of this refresh; just your stack's state will be. yes
Refreshing (experiments):

error: Could not get signed url for stack location: blob (key ".pulumi/stacks/experiments.json") (code=Unknown): to use SignedURL, you must call OpenBucket with a valid Options.GoogleAccessID and exactly one of Options.PrivateKey or Options.SignBytes

I also tried to download a checkpoint file from the storage bucket manually, and then tried to import the stack from this file, but this command also fails:

pulumi stack import --file ~/Downloads/pulumi_history_experiments_experiments-1574820036002431000.checkpoint.json

error: could not deserialize deployment: unexpected end of JSON input

Is there a clean way to ask pulumi cli to give up? Ctrl-C causes pulumi to leave things in pending. Example: typo in k8s namespace. Pulumi waits a while and tries several times, but it is clear on the first failure that it should be stopped.

Hello Peers, I've got a beginner question: How can I create

Deplyments

,

Services

etc. in a specific

namespace

? Hope this isn't to basic of a question

Hi Guys,