faint-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 AMdamp-rain-39201
10/06/2022, 4:58 PMvictorious-dusk-75271
10/06/2022, 7:14 PMhttps://puu.sh/Jopyv/229aeca885.png▾
wet-sunset-4939
10/07/2022, 2:23 AMfierce-xylophone-92490
10/07/2022, 2:24 AMdamp-rain-39201
10/07/2022, 9:34 AMpulumi plugin install resource s24 v0.0.0
.`
Underlying error: error downloading plugin s24 to file: failed to download plugin: b24-0.0.0: 403 HTTP error fetching plugin from https://get.pulumi.com/releases/plugins/pulumi-resource-s24-v0.0.0-darwin-arm64.tar.gz
Thank you for your support in advance!
Best regards,
Balabrave-dawn-64711
10/07/2022, 11:22 AMerror: TypeError: Cannot convert undefined or null to object
at Function.keys (<anonymous>)
at Object.transferProperties (/Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@pulumi/runtime/rpc.ts:43:28)
at /Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@pulumi/runtime/resource.ts:504:27
at Generator.next (<anonymous>)
at /Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@pulumi/pulumi/runtime/resource.js:21:71
at new Promise (<anonymous>)
at __awaiter (/Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@pulumi/pulumi/runtime/resource.js:17:12)
at prepareResource (/Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@pulumi/pulumi/runtime/resource.js:340:12)
at Object.registerResource (/Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@pulumi/runtime/resource.ts:286:24)
at new Resource (/Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@pulumi/resource.ts:401:13)
error: Error: Invoke: Default provider for 'kubernetes' disabled. 'kubernetes:yaml:decode' must use an explicit provider.
at Object.callback (/Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@pulumi/runtime/invoke.ts:159:33)
at Object.onReceiveStatus (/Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@grpc/grpc-js/src/client.ts:338:26)
at Object.onReceiveStatus (/Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34)
at Object.onReceiveStatus (/Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
at /Users/pprazak/repos/reflek/infrastructure-cloud/typesense/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
at processTicksAndRejections (node:internal/process/task_queues:77:11)
This is the relevant fragment of the component:
const glbConfig = pulumi.all([args.namespace, this.internalHostname]).apply(
([ns, hs]) => new kubernetes.yaml.ConfigGroup(
`${publicServiceName}-glb-config`,
{
transformations: [args => {
return {
// failed attempt #1 at a workaround
opts: pulumi.mergeOptions(args.opts, {parent: this})
}
}],
yaml: [
`apiVersion: <http://cloud.google.com/v1|cloud.google.com/v1>
kind: BackendConfig
metadata:
name: ${publicServiceName}
namespace: ${ns}
spec:
healthCheck:
checkIntervalSec: 15
timeoutSec: 15
healthyThreshold: 1
unhealthyThreshold: 2
type: HTTP
requestPath: /health
port: ${args.apiPort || defaultApiPort}
`, `
apiVersion: <http://networking.gke.io/v1beta1|networking.gke.io/v1beta1>
kind: FrontendConfig
metadata:
name: ${publicServiceName}
namespace: ${ns}
spec:
redirectToHttps:
enabled: true
responseCodeName: MOVED_PERMANENTLY_DEFAULT
`]
}, {
parent: this,
transformations: [
(args: ResourceTransformationArgs) => {
return {
// failed attempt #2 at a workaround
opts: pulumi.mergeOptions(args.opts, {parent: this})
} as ResourceTransformationResult
}
],
}
));
I'm setting the provider explicitly on the component:
providers: {
kubernetes: k8sProvider, // make sure we use explicit Kubernetes provider, not the default
},
Looks like the provider set on the component is not propagating to the Yaml.strong-intern-84363
10/07/2022, 2:26 PMexample = aws.cloudfront.OriginAccessControl("example",
description="Example Policy",
origin_access_control_origin_type="s3",
signing_behavior="always",
signing_protocol="sigv4")
Getting this error message, any fix available?
AttributeError: module 'pulumi_aws.cloudfront' has no attribute 'OriginAccessControl'
hundreds-park-36222
10/07/2022, 2:39 PMmagnificent-glass-81378
10/07/2022, 3:34 PMlively-needle-84406
10/07/2022, 5:10 PMvictorious-dusk-75271
10/08/2022, 3:49 AMhttps://puu.sh/JovXW/e5e263f012.png▾
victorious-dusk-75271
10/08/2022, 3:49 AMvictorious-dusk-75271
10/08/2022, 3:50 AMbitter-pharmacist-78980
10/08/2022, 2:46 PMpulumi.Run(func(ctx *pulumi.Context) error {
// Create an object store resource
bucket, err := abstractProvider.NewObjectStore(ctx, "my-object-store", nil)
if err != nil {
return err
}
})
Then, there is a separate layer which determines which provider to use or to use multiple providers for multi-cloud redundancy. (Example selection criteria: price, data center geography, real time service outages)
Does such a thing exist?
Essentially, why should a Pulumi developer need to hard code the provider into the IaC?
Also, looking at https://www.pulumi.com/blog/tag/native-providers/ it seems there has been no blog posts about native providers since the original blog post on Apr 20, 2021. Is this a sign that the native providers are not being prioritized?green-bird-4706
10/08/2022, 11:03 PMboundless-engineer-23836
10/10/2022, 1:37 PMhundreds-gold-80559
10/10/2022, 11:12 PMpulumi up
it thinks we need to delete/re-create the container defn. Here is one of the diff outputs (edited). We compared the diffs across different successful runs of pulumi up
and they are always the same.
[id=pganalyze-fargate]
[urn=urn:pulumi:production::rainbow-infra::awsx:x:ecs:FargateTaskDefinition$aws:ecs/taskDefinition:TaskDefinition::production-pganalyze-service]
__defaults : []
containerDefinitions : "[{"image":"<http://quay.io/pganalyze/collector:stable|quay.io/pganalyze/collector:stable>","cpu":256,"memory":512,"essential":true,"ulimits":[{"name":"nofile","softLimit":32000,"hardLimit":65536}],"environment":[{"name":"DB_HOST","value":"snip},{"name":"DB_USERNAME","value":"pganalyze"},{"name":"DB_NAME","value":"rainbow"}],"secrets":[{"name":"PGA_API_KEY","valueFrom":"snip"},{"name":"DB_PASSWORD","valueFrom":"snip"}],"logConfiguration":{"logDriver":"awsfirelens"},"readonlyRootFilesystem":false,"mountPoints":[],"name":"pganalyze"},{"cpu":128,"memory":512,"image":"<http://XXX.dkr.ecr.us-west-2.amazonaws.com/amazon/aws-for-fluent-bit:2.26.0|XXX.dkr.ecr.us-west-2.amazonaws.com/amazon/aws-for-fluent-bit:2.26.0>","firelensConfiguration":{"type":"fluentbit","options":{"config-file-type":"file","config-file-value":"/log_destinations.conf"}},"environment":[{"name":"SERVICE_NAME","value":"pganalyze"},{"name":"SERVICE_ENV","value":"production"},{"name":"GRAFANA_USER","value":"XXX"},{"name":"GRAFANA_API_KEY","value":"[secret]"}],"essential":true,"logConfiguration":{"logDriver":"awslogs","options":{"awslogs-group":"/ecs/ecs-aws-fluentbit-sidecar-logger","awslogs-region":"us-west-2","awslogs-stream-prefix":"pganalyze","awslogs-create-group":"True"}},"name":"logs"}]"
cpu : "512"
executionRoleArn : "arn:aws:iam::XXX:role/rainbow-pganalyze-role-2961ff0"
family : "pganalyze-fargate"
memory : "1024"
networkMode : "awsvpc"
requiresCompatibilities: [
[0]: "FARGATE"
]
taskRoleArn : "arn:aws:iam::XXX:role/rainbow-pganalyze-task-role-919c4b6"%
Any ideas? What are we doing wrong?brash-toothbrush-39078
10/11/2022, 1:48 AMquaint-salesmen-18327
10/11/2022, 7:50 AMjolly-doctor-17673
10/11/2022, 8:45 AMvictorious-dusk-75271
10/11/2022, 12:01 PMmicroscopic-barista-15731
10/11/2022, 12:53 PM└── common
├── Pulumi.cmn.yaml
├── Pulumi.yaml
├── __main__.py
├── __pycache__
├── kubernetes
│ ├── Pulumi.kubernetes.yaml
│ ├── Pulumi.yaml
│ ├── __main__.py
│ ├── __pycache__
│ └── requirements.txt
└── requirements.txt
I would like to have micro stacks and use the GCP bucket as the backend.
I’m pointing to the same GCP bucket in both Pulumi.yaml files.
Here is stacks list:
pulumi stack ls
NAME LAST UPDATE RESOURCE COUNT
cmn 12 minutes ago 3
kubernetes 22 hours ago 0
in kubernetes
__main__.py
file I have this part of code
stack = pulumi.get_stack()
print(stack)
pulumi.stack_reference(f"cmn")
and I’m getting the error:
pulumi:pulumi:Stack (kubernetes-kubernetes):
error: Program failed with an unhandled exception:
Traceback (most recent call last):
File "/Users/irmas/projects/devops-new/infra/common/kubernetes/./__main__.py", line 16, in <module>
pulumi.stack_reference("cmn")
TypeError: 'module' object is not callable
kubernetes
great-sunset-355
10/11/2022, 1:14 PMorange-airport-64592
10/11/2022, 1:16 PMOutPut.unsecret
, I found some test case in sdk/python/lib/test/test_next_serialize.py
.
class OutputSecretTests(unittest.TestCase):
@pulumi_test
async def test_secret(self):
x = Output.secret("foo")
is_secret = await x.is_secret()
self.assertTrue(is_secret)
@pulumi_test
async def test_unsecret(self):
x = Output.secret("foo")
x_is_secret = await x.is_secret()
self.assertTrue(x_is_secret)
y = Output.unsecret(x)
y_val = await y.future()
y_is_secret = await y.is_secret()
self.assertEqual(y_val, "foo")
self.assertFalse(y_is_secret)
but there are not async function in my pulumi script , I’m not using asynchronous, I don’t know how to use this.