Closed sawilde closed 1 week ago
Hello @sawilde -- We had put out an update that had added the ability to add the extension layer independently of the other layers. The parameter addExtension
is currently defaults to true
. I am going to work on making a change so the parameter is set to false
by default. This should resolve the error.
I apologize for the inconvenience this has caused.
So the fix is to add
addLayers: false
to our templates?
Where is this documented?
Hey @sawilde -- a work around for now is adding the parameter addExtension
to false. I am working on a pr currently to default this parameter to false. so this would be a temporary work around. The documentation is in a pr currently.
And what value should I use for extensionLayerVersion
?
PS sorry for the questions but trying to make sure the all details are available to others seeking a fix/solution
Hey @sawilde -- just as an update. We had just released version 0.14.1 of the cloudformation macro - which addresses this issue and you should now be able to run the macro as you had it previously configured.
Thank you for reaching out and letting us know of this issue.
Expected Behavior
deploys without issue as before
Actual Behavior
fails to deploy and is now requesting the
extensionLayerVersion
field is providedit is not possible to add that field alone as doing so then results in
We do not have these as we are using the datadog-forwarder to take our cloudwatch logs and push them into datadog
Steps to Reproduce the Problem
Specifications
For the Datadog Serverless Macro:
Stacktrace
The problem seems to stem from this PR
https://github.com/DataDog/datadog-cloudformation-macro/pull/131
which now throws an error when
extensionLayerVersion
is not provided.