The dynatrace-bootstrapper
is a small CLI binary built into a Dynatrace CodeModule (after version <to-be-determined-codemodule-version>
) so that it can be used in conjunction with the dynatrace-operator to optimize the download and configuration of a CodeModule in Kubernetes.
- Copy a Dynatrace CodeModule to a target directory
- Configure the Dynatrace CodeModule according to the configuration options provided
Example: --source="/opt/dynatrace/oneagent"
⚠️ This is a required arg⚠️ - The
--source
arg defines the base path where to copy the CodeModule FROM.
Example: --target="example/bins/1.2.3"
⚠️ This is a required arg⚠️ - The
--target
arg defines the base path where to copy the CodeModule TO.
Example: --work="/example/work"
- This is an optional arg
- The
--work
arg defines the base path for a tmp folder, this is where the command will do its work, to make sure the operations are atomic. It must be on the same disk as the target folder.
Example: --technology="python,java"
- This is an optional arg
- The
--technology
arg defines the paths associated to the given technology in themanifest.json
file. Only those files will be copied that match the technology. It is a comma-separated list.
Example: --config-directory="/example/config/dir"
- This is an optional arg
- The
--config-directory
arg defines the path whereenrichment
andconfig
files will be created in.
Example: --attribute="k8s.pod.name=test"
- This is an optional arg
- The
--attribute
arg defines the passed in Pod attributes that will be ultimately stored in the files that are stored in theenrichment
directory. It is a key value pair.
Example: --technology="{k8s.container.name=app, container_image.registry=gcr.io, container_image.repository=test}"
- This is an optional arg
- The
--attribute-container
arg defines the passed in Container attributes that will be ultimately stored in the files that are stored in theoneagent
directory. It is a JSON formatted string.
- To run tests:
make test
- To run linting:
make lint
- To build a testing image:
make build