Dogen

Latest version: v2.4.4

Safety actively analyzes 629723 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 5

2.2.1

Fixed template by removing curly bracket, 168

2.2.0

It is now possible to use local CCT modules, 167.

Instead of cloning CCT modules specified in the image descriptor - you can put your local copy of the module into the `cct/MODULE_NAME` directory created next to the image descriptor. This module, instead of the one specified in image descriptor, will be used to build the image. This is very useful for local image building.

P.S. You can also symlink this module directory if you want. This way you can reuse the same local copy of module in multiple images.

2.1.0

This release makes it easier to work with CCT (Container Configuration Tool).

* Dist-git plugin was extended and it's now possible to specify the repository and branch name to sync with, 147
You can now use the image descriptor to define the repository and branch name for the dist-git plugin:
yaml
dogen:
plugins:
dit_git:
repo: repo-name
branch: branch-name

With the addition of `--dist-git-assume-yes` this will enable non-interactive syncs with dist-git repositories.
* CCT was updated to 0.3.0, 162
* Cleanup of CCT modules after installation, 157

2.0.1

* Logging output is now printed to the correct stream, 144
* Dogen will not fail if the artifact is locally available, but the hash is not specified, 145

2.0.0r6

Changes
- Allow to rename the artifact in `sources` section to be renamed after it'll be fetched, 71

2.0.0

* The `--additional-scripts` option was removed, 133
* The `maintainer` key now generates a `maintainer` label, not the `MAINTAINER` instruction, 129
* The `description` key now generates a `description` label, 137
* Output logs are now colored, 142
* In `sources` section you can now specify a hint for the artifacts - it will be displayed when there is a problem with fetching it, 131
* When downloading fails when the `DOGEN_SOURCES_CACHE` - try to download from original location, 130
* Schema change: in `sources`, the `url` was renamed to `artifact`, 132, example:
yaml
sources:
- url: jboss-eap-6.4.0.zip
md5: 19a5d37631919a111ddf42ceda1a9f0b5

becomes:
yaml
sources:
- artifact: jboss-eap-6.4.0.zip
md5: 19a5d37631919a111ddf42ceda1a9f0b5

* Schema change: environment variables section was simplified, 127 , example:
yaml
envs:
information:
- name: "JBOSS_HOME"
value: "/opt/eap"
configuration:
- name: "DEBUG"
example: "true"
description: "Specify true to enable development mode (debugging)."
- name: "DEBUG_PORT"
example: "8787"
description: "Specify the port to use for debugging. If not set, the default EAP debug port will be used (8787). Only applicable when development mode is enabled."

becomes:
yaml
envs:
- name: "JBOSS_HOME"
value: "/opt/eap"
- name: "DEBUG"
example: "true"
description: "Specify true to enable development mode (debugging)."
- name: "DEBUG_PORT"
example: "8787"
description: "Specify the port to use for debugging. If not set, the default EAP debug port will be used (8787). Only applicable when development mode is enabled."

Page 2 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.