melodic-car-16900
10/02/2022, 6:55 PMlively-winter-28362
10/02/2022, 11:59 PMpulumi up
will protect everything without me asking it to protect them. Any ideas at steps I can take to fix this?kind-jelly-61624
10/03/2022, 12:56 AMdry-dentist-95091
10/03/2022, 8:32 AMids:list[pulumi.output.Output] =[] #contains ids of the resources to be deployed
deployment = apigateway.Deployment("test_deployment",
rest_api=restapi.id,
triggers={
"redeployment":pulumi.Output.all(ids)
.apply(lambda exampleResourceId: json.dumps([exampleResourceId]))
.apply(lambda to_json: hashlib.sha1(to_json.encode()).hexdigest()),
}
)
as pulumi.Output.all function accepts the pulumi.output.Output not list[pulumi.output.Output], I am getting error.
How should I pass the above ids into pulumi.Output.all function so that all the ids in the list can passed?
(a list can contain any number of elements)chilly-analyst-14900
10/03/2022, 11:52 AMdestroy
or rm
. I could ofc do it myself using pulumi stack ls --tag isDevTempEnv true
and then destroy them one by one in a loop.brash-restaurant-84207
10/03/2022, 12:33 PMdamp-rain-39201
10/03/2022, 4:35 PMUpdating (dev)
View Live: <https://app.pulumi.com/Atmakur/s3-service/dev/updates/2>
Type Name Status
pulumi:pulumi:Stack s3-service-dev
Resources:
1 unchanged
Duration: 1s
stale-orange-47562
10/03/2022, 6:09 PMwet-sunset-4939
10/04/2022, 1:10 AMpanic: interface conversion: interface {} is nil, not []interface {}
goroutine 242 [running]:
<http://github.com/hashicorp/terraform-provider-azurerm/internal/services/containers/migration.KubernetesClusterV1ToV2.UpgradeFunc.func1({0x6eee980|github.com/hashicorp/terraform-provider-azurerm/internal/services/containers/migration.KubernetesClusterV1ToV2.UpgradeFunc.func1({0x6eee980>?, 0xc0028888c8?}, 0x5c70b80?, {0xc0029ccfc0?, 0x6eee980?})
/home/runner/go/pkg/mod/github.com/pulumi/terraform-provider-azurerm@v1.41.1-0.20220923214953-9abea3c6f19c/internal/services/containers/migration/kubernetes_cluster.go:1231 +0x2fe
<http://github.com/hashicorp/terraform-provider-azurerm/internal/tf/pluginsdk.StateUpgrades.func1({0x6eeb650|github.com/hashicorp/terraform-provider-azurerm/internal/tf/pluginsdk.StateUpgrades.func1({0x6eeb650>, 0xc000138028}, 0x2?, {0x5c19d60, 0xc000e4ae00})
elegant-action-99227
10/04/2022, 5:41 AMgorgeous-accountant-60580
10/04/2022, 8:01 AMdamp-honey-93158
10/04/2022, 1:38 PMbillions-journalist-44569
10/04/2022, 1:50 PMpulumi state delete <urn>
programmatically in Python or via REST API?sparse-gold-10561
10/04/2022, 2:09 PM[diff: ~__provider]
it seems to try to update the resource even though the its only the provider version that has changed. I notice on the official providers, these type of diffs get ignored.fast-river-57630
10/04/2022, 2:53 PM... (...-vpc):
error: expected '::' in provider reference ''
Maybe you can't replace a resource from the AWS provider for one from a different provider? or is my aliases: wrong?millions-guitar-3468
10/04/2022, 4:38 PMlimited-salesmen-97945
10/04/2022, 6:39 PMuser_project_override
to true in the provider config. Does anyone have an example?
Link to doc: https://www.pulumi.com/registry/packages/gcp/api-docs/billing/budget/some-pizza-35589
10/04/2022, 7:09 PMmagnificent-glass-81378
10/04/2022, 7:44 PMpulumi up
) it will use the new value, correct?
If that's true, then is there some way to take advantage of outputs and stack references that still allows for a looser coupling? My goal is to strongly limit the blast radius of stack changes. I'd like to be that if we change one stack, that those changes don't automatically ripple to many others. What's the best practice here?creamy-byte-37608
10/04/2022, 8:08 PMaverage-tiger-58107
10/04/2022, 9:13 PMapply
? Example:
const scsExecPolicy = pulumi
.all([commonClusterExecKey.arn, commonClusterEcsExecLogGroup.arn])
.apply(([commonClusterExecKeyARN, commonClusterEcsExecLogGroupArn]) => {
return new aws.iam.Policy("scs-exec-policy", {
name: "cfx-policy-scs-exec",
policy: JSON.stringify({
Version: "2012-10-17",
Statement: [
{
Action: [
"ssmmessages:CreateControlChannel",
"ssmmessages:CreateDataChannel",
"ssmmessages:OpenControlChannel",
"ssmmessages:OpenDataChannel",
],
Effect: "Allow",
Resource: "*",
},
{
Action: ["logs:DescribeLogGroups"],
Effect: "Allow",
Resource: "*",
},
{
Action: [
"logs:CreateLogStream",
"logs:DescribeLogStreams",
"logs:PutLogEvents",
],
Effect: "Allow",
Resource: `${commonClusterEcsExecLogGroupArn}:*`,
},
{
Effect: "Allow",
Action: ["kms:Decrypt"],
Resource: commonClusterExecKeyARN,
},
],
}),
});
});
damp-rain-39201
10/04/2022, 11:23 PMfierce-xylophone-92490
10/05/2022, 1:35 AMbrash-television-56562
10/05/2022, 2:29 PMfaint-balloon-33174
10/05/2022, 2:47 PMlively-needle-84406
10/05/2022, 3:02 PMistio-system
, but a randomly generated string gets appended to the name. Is there a way to specify a specific name for a namespace when using new kubernetes.core.v1.Namespace
?
const istioNamespaceName = "istio-system"
const istioNamespace = new k8s.core.v1.Namespace(istioNamespaceName);
const istioVersion = "1.15.0";
const istioBase = new k8s.helm.v3.Chart("istio-base", {
chart: "base",
version: istioVersion,
namespace: istioNamespaceName,
fetchOpts: {
repo: "<https://istio-release.storage.googleapis.com/charts>",
},
}, {
dependsOn: istioNamespace
});
microscopic-piano-27908
10/05/2022, 5:57 PMpulumi up
I get:
error modifying Lambda Function (lambda-name) Code: RequestEntityTooLargeException: status code: 413
If I run pulumi up
again, it looks like the changes go through:
Type Name Status Info
pulumi:pulumi:Stack lambda-name
~ ├─ aws:lambda:Function lambda-slash-commands updated [diff: ~code]
~ └─ aws:lambda:Function lambda-cron updated [diff: ~code]
Resources:
~ 2 updated
17 unchanged
If I then go and look for the changes in the Slack App, they’re not there.
Side Note - I know I need to address the RequestEntityTooLargeException
. I tried adding webpack to reduce the build size but that resulted in an error where Webpack doesn’t know what to do with @pulumi/aws
and that dead-ended me there.
Any thoughts on why the updates appear to successfully go through but don’t?icy-boots-7501
10/05/2022, 7:34 PMpulumi refresh
and then try to run pulumi up
I have been getting this error.
Running pulumi destroy
first allows me to successfully use pulumi up
but it is annoying to have to do this, especially with certain resources that take a long time to remove and deploy. This also doesn't seem to happen if I don't run the refresh
before running the up command.
Can anyone provide insight into what this error is and/or what might be causing it?
I am using Pulumi 3.40.1. We are deploying resources to azure using the Azure-Native and pulumi standard packages.
Let me know what other information I can provide in order to diagnose this issue.
Thanks in advance.witty-barista-69390
10/05/2022, 10:31 PMadamant-portugal-44732
10/06/2022, 6:03 AMadamant-portugal-44732
10/06/2022, 6:03 AM