v0.1.7

Changelog

• The cli now supports a local configuration file, copl.yaml. Best practice is to keep that at the root of your repo.
• The cli reads the git repo url from the git details. or you can use COPL_GIT_REPO to overwrite.
• The session environment can read from an account local ECR. The EC2 instance needs to have the right level of permissions.
• The session environment downloads the compressed dependencies from S3 and extracts before the hot pod starts.
• CHORE: Copl has a dynamic configuration API now. This seamless to user but allows to customise so many things for the back end.
• Thanks to the dynamic configuration API, it supports two Github authentication methods - device flow and installation token. Device flow forces the user to interact with GitHub before giving permissions, just like a consent form. The latter is a seamless one but requires the PAT for your repo to be stored at the dynamic configuration API.
• For device flow, CLI writes the code to the clipboard.
• Backend architecture, as stated in the copl.yaml file we introduced two new constructs - build and hot pod. Hot pod is the container that hosts the application that is tested or developed. Build is the process that prepares the session environment before the hot pod starts.
• Soon: a new API that converts docker compose files to copl helm charts.