Skip to content

Release 2.6.0
Compare
Choose a tag to compare
@monaco-release-dt-bot monaco-release-dt-bot released this 02 Aug 08:58
· 819 commits to main since this release
v2.6.0
This tag was signed with the committer’s verified signature.
UnseenWizzard Nico Riedmann
SSH Key Fingerprint: lrR1MRVNaOymC7KffOLQ1y3iSWhUEpKQZNjJC9fHlKc Learn about vigilant mode.
6fc98fb
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's Changed

🚀 Features

Support for Workflows/Automations

The Dynatrace Platform introduced Dynatrace Automations and Workflows.

Workflows, business-calendars and scheduling-rules can now also be managed as configuration as code.

The best way to get started is to download configurations from a Platform environment where you have configured a workflow.

You can also take a look at this sample project.

For more on configuration as code for automation see the documentation.

Improved deployment

We've implemented several improvements for the Monaco deployment - all focused on making deployments faster and more resilient.

Graph-based sorting

We improved the internal representation of configurations and dependencies to a graph data structure.

This is used when sorting configurations for deployment, which is notably faster and more memory efficient that the previous sorting.

This feature is active by default but can be disabled via the environment variable feature flag MONACO_FEAT_GRAPH_SORT=false.

Further improvements to deployment using the new graph representation will be part of upcoming releases.

Updating Settings with unique key properties

Some Settings 2.0 schemas define unique key constraints, which ensure that Settings objects are unique.

Monaco is now aware of these constraints and can identify and update existing objects based on their unique keys, instead of just by externalID or originObjectID.

Previously if an object with an overlapping unique key already existed, monaco would attempt to create a duplicate, resulting in an API error.

This new behavior is conceptually similar to classic Config API objects being identified based on their name.

Improved caching

Monaco made several repetitive queries during deployments to identify and update existing configurations.
These are heavily reduced by introducing caching.

Generate a dependency graph for your Monaco configurations

The command monaco generate graph <manifest.yaml> can create dependency graphs of your configurations. They're exported using the DOT format.
You can use a tool of your choice to visualize the graph as an image - for example graphviz online.

For more on this command see the documentation.

Generate delete-files for your Monaco configurations

The command monaco generate deletefile <manifest.yaml> can create delete files for your Monaco projects.

For more on this command see the documentation.

Container image

Images are available at https://hub.docker.com/r/dynatrace/dynatrace-configuration-as-code

The image can be used directly, passing command arguments to the CLI directly or in CI with a monaco executable available in the container.

docker pull dynatrace/dynatrace-configuration-as-code:2.6.0

Verifying Signature

The Image is signed, and its signature can be verified using cosign and the cosign.pub key that can be downloaded from this release.

 cosign verify --key cosign.pub dynatrace/dynatrace-configuration-as-code:2.6.0

Full Changelog: v2.5.0...v2.6.0

Assets 17
Loading