Tags: houjun1988325/aws-saas-boost
Tags
Fixing EC2 launch type and Windows provisioning. Upgrading to use EC2… … Launch Templates and also support EC2 for Linux workloads (still hard coded to use Fargate for Linux).
Upgrade aws-lambda-java-log4j2 to 1.5.0 to upgrade log4j2 to 2.17.0 (a… …wslabs#166) * upgrade aws-lambda-java-log4j2 to 1.5.0 to upgrade log4j2 to 2.17.0 * apply logging standardization across all connected modules * Upgrade log4j2 to 2.17.1 and aws-lambda-java-log4j to 1.5.1 * exclude log4j-core and api from lambda logging, use from log4j-slf4j-impl * Remove explicit log4j-slf4j-impl from custom-resources * Move log4j-slf4j-impl to layers parent and mark as provided to avoid class conflict Co-authored-by: PoeppingT <[email protected]>
Bump log4j-core from 2.13.3 to 2.15.0 in /installer (awslabs#156) * Bump log4j-core from 2.13.3 to 2.15.0 in /installer Bumps log4j-core from 2.13.3 to 2.15.0. --- updated-dependencies: - dependency-name: org.apache.logging.log4j:log4j-core dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> * Bump log4j-api from 2.13.3 to 2.15.0 in /installer (awslabs#155) Bumps log4j-api from 2.13.3 to 2.15.0. --- updated-dependencies: - dependency-name: org.apache.logging.log4j:log4j-api dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Change import checkstyle configuration and fix all import violations (a… …wslabs#136) * change import checkstyle * update import order rules and fix all ImportOrder checkstyle violations * add a comment about checkstyle to CONTRIBUTING.md * Change hyperlink to checkstyle.xml for clarity * reduce allowed checkstyle violations to the current violations Co-authored-by: Thomas Poepping <[email protected]>