fixing naming

Dockerfile

@@ -8,6 +8,6 @@ RUN wget https://github.com/stedolan/jq/releases/download/jq-1.7/jq-linux64 && \
   mv jq-linux64 /usr/local/bin/jq && \
   chmod +x /usr/local/bin/jq
 
-COPY ./load-env.sh load-env.sh
+COPY ./parse-config.sh parse-config.sh
 
-ENTRYPOINT [ "bash", "load-env.sh" ]
+ENTRYPOINT [ "bash", "parse-config.sh" ]

README.md

@@ -1,4 +1,4 @@
 ## Overview
-The `parse-env.sh` script is used as an init container to create a `.env` file from other config files. In our current setup, these other config files are K8S secrets mounted as volumes. The format of the resulting `.env` file is a traditional `KEY=VALUE` text file, with each entry being seperated by a new line. This way, applications need to be only aware of one file to load its configuration. Aside from the bundling, the script also formats the key to standardise naming.
+The `parse-config.sh` script is used as an init container to create a `.env` file from other config files. In our current setup, these other config files are K8S secrets mounted as volumes. The format of the resulting `.env` file is a traditional `KEY=VALUE` text file, with each entry being seperated by a new line. This way, applications need to be only aware of one file to load its configuration. Aside from the bundling, the script also formats the key to standardise naming.
 
 Note that for the moment we only parse one other config file coming from SSM, but we might add other later.