cloudformation-cli-java-plugin
cloudformation-cli-java-plugin copied to clipboard
The CloudFormation Provider Development Toolkit Java Plugin allows you to autogenerate java code based on an input schema.
Hi! At the moment there's no way of co-relating log entries outputted from the handler. An invocation (without customer log calls would look like: ``` 2020-01-14T19:14:17.627+01:00 | Record Handler Progress...
Version 1.0.5 of the Java plugin Schema: ``` { "typeName": "OBFUSCATED::ApiGateway::RestApi", "description": "An example resource schema demonstrating some basic constructs and validation rules.", "sourceUrl": "https://github.com/aws-cloudformation/aws-cloudformation-rpdk.git", "properties": { "RestApiId": { "type":...
LoggerProxy provides logging capability. However, some libraries especially [AWS SDK uses Log4j](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-logging.html) for their logging. To enable log4j for resource handler, a Log4j appender should be provided so it can...
The documentation generated by `mvn javadoc:javadoc` is missing the methods auto-generated by Lombok. So, the documentation is missing methods like `builder()` that are used in our examples. There's a [Maven...
Issue #221 deals with not logging information that is marked as a `writeOnlyProperty`. The resource I'm developing has a `readOnlyProperty` that is sensitive and should not be logged. How do...
A dry-run capability can be introduced to the LambdaWrapper layer, which would bypass the actual handler invocation. It would return canned success/failure responses and emit metrics/logs. This can be used...
This is the property that I’m trying to define: "Canceled": { "description": "POSIX Timestamp of cancellation of this downtime (null if not canceled)", "type": ["integer", "null"] }, This should be...
Currently, although CloudFormation will eventually timeout on waiting for a resource provisioning action, there is no constraint on the duration or number of re-invocations that can be scheduled, leading to...
It is necessary to test if the user-defined callbackContext passed back into the handler during reinvocation is serializable. A generated test should be added to test for this so that...
*Description of changes:* Ensure that we null out model for AlreadyExists error to meet CFN expectations. I changed the order of the imports for spotless to be in alphabetical order...