All notable changes to this project will be documented in this file.
- Replace hub with gh in the release script: #42.
- Detect and report errors reading mergeable sources: #41.
- Fix the logic in the function that checks if a file ends with
.edn: #36.
- Add option to define options for the Clojure compiler when building and containerizing an application: #32. See the Clojure documentation for more details.
- Use the newly created function misc/read-data to read/merge data_readers instead of the misc/read-edn function. The former preserves reader conditionals #31.
- Resources with the extension
.ednare deep merged together: #29.
- Exposes command for building Clojure application
build: #26.
- Add support for compiling Java source files present on the classpath: #25.
- Along with the changes made in #25, a new namespace named
shwas introduced. As of this pull request, Vessel spawns a subshell to run Java in order to callclojure.core/compilerather than using a separate classloader.
- Accept tarballs as base images: #23. This feature will be less obscure and easier to be used in the version 1 of Vessel.
- Preserve the order of classpath entries to avoid introducing conflicts: #24.
- Avoid blowing up the build process when a non-mapped class file is found #22. Now, the non-mapped file is assigned to the first known source directory in order to force the file to be copied to the corresponding image layer.
- Preserve timestamps when copying files: #21. The corresponding issue was slowing down the startup of containerized applications and causing runtime problems due to conflicts between AOT and JIT compiled Clojure namespaces.
- #15: added the user option to set the default user image
- #10: added out of the box
integration with Amazon Elastic Container Registry. Vessel looks up
credentials to access AWS API the same way the
awscliorJava SDKdo. Thus, Vessel is capable of obtaining credentials to accessECRrepositories through instance profiles without additional configurations, what might be useful to eliminate extra steps on CI pipelines.
- Integration tests.
- Workflow file to run tests automatically on Github Actions.
- Normalize keys of the manifest.json file in order to avoid incongruities. Thus, Vessel can be employed as a generic alternative to push tarballs to remote registries.
- Added the
--preserve-file-permissionsflag to thecontainerizecommand. By default, files are copied to the container with the permissions 644. When this flag is enabled, Vessel copies files with their original permissions. This feature is useful, for instance, to keep executable scripts (e.g. wrappers for calling the java command) with their original permissions within the container.
- Push command to upload a tarball to a registry.
- Internal: rename vessel.jib namespace to vessel.jib.containerizer and move functions that deal with common aspects of Jib API to the new vessel.jib.helpers namespace.
- Upgrade Jib to version 0.13.0.
- Set the directory for caching base image and application layers to ~/.vessel-cache. Eventually, Vessel can take this directory as a parameter to allow a more fine-grained customization.
- Containerize, image and manifest commands (Vessel is in an alpha stage; the API is subject to changes).