Open msummers-nr opened 2 years ago
You should probably use the cloudformation-cli-go-plugin
- the lambda cfn
package pre-dates the feature for publishable CloudFormation resources, so I'm sure there's drift. Not sure right now what the exact differences are. If it's a small difference, then it makes sense to bring the aws-lambda-go/cfn
up to parity. But it may be that it's a totally different feature that requires the use of cloudformation-cli-go-plugin
.
I've written a custom resource using the cfn package. We want to publicly publish the custom resource but cannot get the
cfn test
contract test suite to run (I do have a rpdk json file). The best I can tell our code is not called at all.Every test fails with
Lambda's output is always
None of my logging shows-up in the lambda's output.
Do I need to fallback to cloudformation-cli-go-plugin?