eager-parrot-83525
10/09/2021, 5:19 PMcrooked-pillow-11944
10/10/2021, 3:34 AMquaint-electrician-41503
10/11/2021, 5:20 PMdry-autumn-28966
10/11/2021, 6:54 PMmillions-furniture-75402
10/11/2021, 8:44 PMunit
is not in the returned JSON.
If I edit the properties in the dashboard source, I can add "unit": "Percent"
and the dashboard honors this. However, this feature is undocumented: https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/CloudWatch-Dashboard-Body-Structure.html#CloudWatch-Dashboar[…]dering-Object-Format
So I'm confused about whose bug/feature this really is.quaint-electrician-41503
10/12/2021, 9:10 AMable-planet-19148
10/12/2021, 2:30 PMmillions-furniture-75402
10/12/2021, 2:50 PMfromDockerBuild
appears to hang if I pass a aws.ecr.Repository
instead of a string
for the first argument:
const containerRepository = new aws.ecr.Repository(`${appName}-image`, {
imageScanningConfiguration: {
scanOnPush: true,
},
imageTagMutability: "MUTABLE",
});
new awsx.ecs.FargateService(
`${appName}-service`, {
...
image: awsx.ecs.Image.fromDockerBuild(containerRepository, buildArgs);
...
}, { dependsOn: containerRepository });
Any idea what I'm doing wrong?green-musician-49057
10/12/2021, 5:15 PMquaint-electrician-41503
10/12/2021, 11:00 PMDiagnostics:
pulumi:pulumi:Stack (quickstart-dev):
error: Error serializing '(event) => __awaiter(void 0, void 0, .
'(event) => __awaiter(void 0, void 0, ...': index.ts(20,19): cap
'spawn', a function defined at
function 'spawnWithSignal': child_process.js(900,24): which
'validateAbortSignal', a function defined at
'(signal, name) => { if (signal !== u ...': which captur
'ERR_INVALID_ARG_TYPE', a function defined at
function 'NodeError': which referenced
function 'getMessage': which captured
variable 'messages' which indirectly referenced
function 'get': which could not be serialized
it was a native code function.
Function code:
function get() { [native code] }
great-sunset-355
10/13/2021, 10:54 AM"applyMethod": "pending-reboot"
to `"applyMethod": "immediate"
The affected parameter is timezone
which I create like this:
{"name": "timezone", "value": "UTC"},
And according to docs the default applyMethod
value is set to immediate
.
So the questions are:
1) What did set applyMethod
to pending-reboot
?
2) Why does pulumi try to change the value every time? (I'd say it may be coming from the provider)
3) And where can I find which parameters require reboot?able-planet-19148
10/13/2021, 1:00 PMadditionalInstanceConfiguration
property on aws.imagebuilder.ImageRecipe.
See: https://www.pulumi.com/docs/reference/pkg/aws/imagebuilder/imagerecipe/damp-school-17708
10/13/2021, 1:28 PMworried-city-86458
10/13/2021, 6:28 PMdamp-school-17708
10/14/2021, 12:03 PM@pulumi/aws ^4.22.1 → ^4.24.1
@pulumi/pulumi ^3.13.2 → ^3.14.0Same for us, we had Node 14.x and the layer
49
. I switched to 64
just to make sure it wasn't the layer version, but it quickly became evident that the version didn't matter. Since there was no code change on our side before and after the errors started showing up, we believe it's infra related.
The layer is still there, and you can't modify it AFAIK so this must be AWS.
We opened a ticket with AWS. I think they're are doing some changes to Lambda and this might be related
You are receiving this message because we identified that your account created or updated or invoked Lambda functions on or after July 1, 2021.
AWS Lambda is extending the capability to track the current state of a function through its lifecycle to all functions [1]. With this change, you may need to update your CLI and/or SDK-based automation workflows around creating and updating functions by adding a check that the function became active before performing additional actions that operate on the function.
Previously, states have been used in two primary use-cases. Firstly, to move the blocking setup of VPC resources out of the path of function invocation. Secondly, to allow the Lambda service to optimize new or updated container images for container-image based functions, also before invocation. By moving this additional work out of the path of the invocation, customers see lower latency and better consistency in their function performance.
Infrastructure as code and deployment automation tools such as AWS CloudFormation, AWS Serverless Application Model (SAM), AWS Cloud Development Kit (CDK), Serverless Framework,Hashicorp Terraform, AWS Chalice and Cloud Custodian already support states.
If you are using these tools and are already on the latest Software Development Kit (SDK), you do not need to take any action, and can stop reading now. If you are using an earlier SDK version, please update to the latest one.
We are rolling out this change over multi-phase periods to allow you to update existing tooling for deploying and managing Lambda functions. You can delay this change for your functions until December 5, 2021. Starting December 6, 2021, the delay mechanism expires and all customers see the Lambda states lifecycle applied during function create or update. Read this blog post [2] to learn about this change, timelines for different phases and a reference example on how to check your function state.
and then the support also said
Furthermore, Lambda team performed rollback to fix this issue but this may take some time to fully propagate. However, I am actively monitoring internal ticket and I will keep you updated on this case.
freezing-van-87649
10/14/2021, 1:40 PMbrave-nightfall-19158
10/15/2021, 3:14 PMlimited-rainbow-51650
10/17/2021, 4:04 PMaws-native
provider have support for AWS CodeCommit and CodePipeline? At first glance, I couldn't find the corresponding module for these services in the docs.
https://www.pulumi.com/docs/reference/pkg/aws-native/purple-plumber-90981
10/18/2021, 5:52 AMproviders = pulumi.StackReference('aws-providers')
and then opts=pulumi.ResourceOptions(provider=providers.get_output('provider_aws_us-east-1'))
???flat-appointment-12338
10/18/2021, 9:07 PMearly-keyboard-41388
10/19/2021, 9:19 AMStackReference
(trying to understand it). I’m using S3 as backend (everything in one bucket), ideally a folder for each project (micro services setup: infra, app, services, etc).
With this I saw two options:
1. Every pulumi project in same folder -> each stack needs to have project name in it (eg, infra.dev
), or they will collide (dev, in two different projects, in same folder in S3).
2. Every project in different folders -> stack can be named with just the environment (dev
, stg
, prod
)
In case 1, I did new StackReference('infra.dev')
, and it ends with error:
aws:lambda:Function (lambda_name):
error: 1 error occurred:
* error creating Lambda Function (1): ValidationException:
status code: 400, request id: 6dab7a4b-c6cc-4ebc-8a46-cb14060d50f2
Apparently it gets the stack_reference but it fails to deploy. My assumption is because it’s empty data or failing in some level with those refs.
Also tried new StackReference('project_name/infra.dev')
, but got the error:
error: Preview failed: unknown stack "project_name/infra.dev"
If I wanted to use the case 2, everything in different folders, how do you reference to the other stack?
Any help is more than welcome.brainy-window-77332
10/19/2021, 1:34 PMbrainy-window-77332
10/19/2021, 1:35 PMmillions-umbrella-34765
10/19/2021, 9:50 PMworried-city-86458
10/20/2021, 1:56 AMPulumi.Aws
(when not using a CloudFormation resource)?
i.e. if I was to port from CF to non-CF using Pulumi, would it be possible to preserve this behaviour?early-keyboard-41388
10/20/2021, 11:46 AMnew
aws.lambda.LayerVersion
. The error is this one.
Error creating lambda layer: ValidationException:
status code: 400, request id: 7e256205-6800-460e-ad82-91ba69f1ac8a
The issue is with the LayerName, options tried:
• [FAIL] layerName: my-layer-${env}
• [FAIL] layerName: myVarName -> where
const myVarName = `my-layer-${env}`.toString() // with or without toString()
• [OK] layerName: “my-layer”
So only valid option is by sending a string in the args
on LayerVersion
.
Any idea on what’s going on?early-keyboard-41388
10/20/2021, 11:57 AMpowerful-furniture-83753
10/20/2021, 12:51 PMlatest
tag isn't updating the lambda. How can we force the lambda to refetch the docker image? Or do we have to have well named version tags and that then forces the lambda to update?millions-umbrella-34765
10/20/2021, 5:11 PMundefined
for a couple of service principals. Is that a bug?millions-umbrella-34765
10/20/2021, 6:30 PM