update aws pom to resolve log4j issues
Type of change
-
Bug Fix -
Feature
Please provide link to gitlab issue or ADR(Architecture Decision Record)
Does this introduce a change in the core logic?
- NO
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- NO
What is the current behavior?
Runtime exceptions in aws GCZ due to not having correct logging dependencies available
What is the new/expected behavior?
No more exceptions on startup in AWS GCZ
Have you added/updated Unit Tests and Integration Tests?
N/A
Any other useful information
Deployed to local aws instance and see the exceptions resolved