This release focuses on documentation improvements, especially in for modules. Other bigger change is that this we have fixed Dockerfile generation so that the Docker layer cache can be reused.
3.3.0 was never released due to the fact that we encountered issues with PyPi which made it impossible to push version
3.3.0 again. There are no changes in the code between version
Please see below for all changes that went in.
- Template used to generate Dockerfile was updates so that we can now utilize properly Docker layer cache, #544
- ZSH completion was fixed and it should work now, #554
- A new switch to the
buildcommand was added:
--validate. It is responsible for checking that the image descriptor (and relevant modules) are correct. It does not generate files for the specific builder.
- Documentation around module versioning was added, #194, #196
- Documentation was updated on best practices regarding module naming, #197
- A warning is now printed when artifact does not define a
namekey. This is to remind you that in order to make overrides work nicely, you should define it, #198
- Documentation covering local module development was extended, #527
- All available Docker builder engine environment variables are now documented, #526
- A workaround was added for
microdnfwhere it fails with message similar to
error: cannot move /var/cache/yum/metadata, #560
- A warning was added when CEKit finds that the
certifilibrary is found -- in most cases it will lead to certificate validation issues related to missing CA certficates, #577
- Image help pages were overhauled. These contain now information about environment variables and labels defined in image modules too. Help page formatting was updated too. These should now provide full information about the image. #528
--tech-previewswitch in the OSBS builder is now deprecated. It will be removed in CEKit 3.5 or later. Overrides should be used instead of this switch.
- Dependency handling was updated to be more flexible, for example we no longer require the
docker-squashlibrary when you do not want to squash the image after building in Docker, #576
- Small tweaks to getting started guide were applied, #556
- Please note that although in documentation we have stated that module's
versionkey is required, we did not enforce it until now. This has been fixed and the
versionkey requirement is enforced.