Update AWS Provider to use S3 for configuration files
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, fixes one
What is the current behavior?
AWS Provider is not built to handle dynamic configuration files
What is the new/expected behavior?
AWS Provider handles dynamic configuration files by using s3 instead of configmap
Have you added/updated Unit Tests and Integration Tests?
N/A
Any other useful information
This commit removes an initContainer from aws helm chart that was previously used to seed initial config files from a configmap. instead, these initial files are uploaded to s3 where they are read on app container start up