As a user I might have a series of files that I bundled together in a ZIP or TAR format, and I would like to be able to extract the archive content to a given directory.

In some cases, such as storing template into SSM which does not support {{}} in a Sting parameter, it could be useful to encode to base64 the template before executing Jinja etc.

Therefore the decoding should be happening first and then evaluate the context.

I want to be able to define that one file depends on the presence of another before acquiring.

files:
  /path/to/A: {}
  /path/to/B:
    depends_on:
      - /path/to/A

This sidecar could also be very helpful in a K8s context. Creating a HELM chart would allow to enable users to use this in their K8s/EKS context.

I would like to be able to retrieve files from a GIT source.

• git+ssh://
• git+https://
• git+http://
• codecommit://

One must agree on:

• When using SSH, I understand that I need to provide the private and public key for the authentication to work.
• When authentication required, I understand that I must provide username/passwords

When using CodeCommit, the IAM role used by the task must provide access to the necessary resources on AWS.
For codecommit, will use https://github.com/aws/git-remote-codecommit as library to retrieve the URL to peform the clone.

Is your feature request related to a problem? Please describe.
Some applications such as NGINX / Apache might want to use SSL even self-signed.
I would like to be able to generate a self-signed certificate that the application can then use simply to enable SSL on endpoint.

As a developer I might be using an application (3rd party or else) that cannot use environment variables.
So I created a template file, that should use variables that a render engine such as Jinja can use to render a final version of the configuration needed by the application