full-dress-10026
11/27/2019, 2:40 AMpulumi 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.full-dress-10026
11/27/2019, 3:06 AMbrainy-microphone-27448
11/27/2019, 1:26 PMVolumeInUse
) when reaattaching existed volume to new instancebroad-finland-69602
11/27/2019, 4:03 PMmillions-judge-24978
11/27/2019, 5:58 PMsteep-printer-55468
11/27/2019, 6:38 PMsteep-printer-55468
11/27/2019, 6:38 PMsteep-printer-55468
11/27/2019, 6:39 PMsteep-printer-55468
11/27/2019, 6:40 PMsteep-printer-55468
11/27/2019, 6:40 PMsteep-printer-55468
11/27/2019, 6:43 PMconst 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'.
}],
},
}
});
steep-printer-55468
11/27/2019, 6:44 PMcurved-zoo-38252
11/27/2019, 10:27 PMpulumi.StackReference
?green-morning-1318
11/27/2019, 10:49 PMsteep-caravan-65104
11/28/2019, 2:05 AMCould 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
steep-caravan-65104
11/28/2019, 2:43 AMpulumi stack import --file ~/Downloads/pulumi_history_experiments_experiments-1574820036002431000.checkpoint.json
error: could not deserialize deployment: unexpected end of JSON input
rhythmic-hair-33677
11/28/2019, 4:37 AMhandsome-cat-98152
11/28/2019, 9:46 AMDeplyments
, Services
etc. in a specific namespace
?
Hope this isn't to basic of a questionswift-lunch-74411
11/28/2019, 9:56 AMswift-lunch-74411
11/28/2019, 9:57 AMswift-lunch-74411
11/28/2019, 10:01 AMswift-lunch-74411
11/28/2019, 10:01 AMquaint-artist-58613
11/28/2019, 10:09 AMimport * as k8s from "@pulumi/kubernetes";
import * as pulumi from "@pulumi/pulumi";
const env = pulumi.getStack();
const infra_stack = new pulumi.StackReference(`acmecorp/infra/${env}`);
const provider = new k8s.Provider("k8s", { kubeconfig: infra.getOutput("kubeConfig") });
const service = new k8s.core.v1.Service(..., { provider: provider });
If infra_stack is deployed in aws account A and current stack is deployed in aws account B, does the code snippet still work?🙂brainy-microphone-27448
11/28/2019, 10:28 AMuserdata
change(and instance recreation)?
https://github.com/avolkov-dev/pulumi-mount-issue/blob/master/index.ts#L16
Because now (without forceDetach
) we are getting Error waiting for Volume (vol-xxx) to detach from Instance: i-xxx error) I believe this is because we trying to detach volume on running instance and getting timeoutedred-football-97286
11/28/2019, 10:57 AMbroad-finland-69602
11/28/2019, 12:15 PMwhite-balloon-205
get_caller_identity
is the answer to how to dynamically get the AWS account id. @broad-finland-69602 what question do you have on how to integrate that? You should just be able to call the function.red-football-97286
11/28/2019, 1:54 PMfrom pulumi_aws import get_caller_identity
current = get_caller_identity()
important-leather-28796
11/28/2019, 9:44 PMwarning: resource plugin kubernetes is expected to have version >=1.3.1, but has 0.20.3-dev.1550685910+g50fc5e2.dirty; the wrong version may be on your path, or this may be a bug in the plugin
I did a pulumi plugin rm --all
and pulumi plugin install
but same occurred, need to rebuild node modules?plain-eye-9759
11/29/2019, 11:18 AMpulumi up
failed for some reason in the first run, and the database account managed to slip through. Subsequent pulumi up
tried to create that same resource and failed because of name uniqueness.
pulumi refresh
didn't work either
How can I handle this?