2.15.1

What's Changed

• Avoid duplicate config downloads and template file overwrites by @warber in #1432
• Choose to exclude skipped configurations from the dependency graph by @warber in #1542
• Increase performance of settings download by @warber in #1541

---

⚠️ No Container image available for this version ⚠️

Due to an issue in our release process, this bugfix release is currently not available on Docker Hub!
We're sorry for this inconvenience and working on a fix.

---

Full Changelog: v2.15.0...v2.15.1

2.15.0

What's Changed

🚀 New Features

• Support for 3rd gen dashboards and notebooks 📊 📔
• Support for OpenPipeline configurations

⚙️ Improvements and 🐛 Bug Fixes

• Better name parameter validation to detect classic config name clashes #1530
• Generate explicit dependencies between builtin:networkzones and network-zone configs during download #1515

Full Changelog: v2.14.3...v2.15.0

2.14.3

🐛 Bug Fixes

• Fixed an error causing account resources deployment to fail. A change in the API schema specification caused monaco to fail fetching allowed/supported permission values during deployment #1516

Full Changelog: v2.14.2...v2.14.3

2.14.2

⚙️ Improvements and 🐛 Bug Fixes

• Improved support archives coverage. Support archives are now closed as late as possible to ensure they contain all log messages.
• Log partial download failures as warnings. Failures which still allow configuration downloads to continue are logged as warnings rather than errors.

Full Changelog: v2.14.1...v2.14.2

2.14.1

🐛 Bug Fixes

• Fixed an error that occurred when downloading ordered Settings objects. If some objects were skipped during download, an index out of range caused a panic.

Full Changelog: v2.14.0...v2.14.1

2.14.0

⚠️ Known issue Downloading some ordered Settings with this version can cause an error that fails the download. We are working on a fix and recommend using 2.13.0 for downloads until that time.

---

🚀 New Features

• Monaco now supports ordering of Settings 2.0 objects via the insertAfter reference parameter. See the docs for details

• New file parameter type that is dynamically resolved to the contents of a file. See the docs for details

• Specific Automation and Settings objects may be deleted by their Dynatrace ID, by defining their objectId rather than configuration id in delete files. For example, to delete a workflow Automation resource with ID 6d9995b4-cd3e-4071-8fe3-82be7e762e67, use:

  - type: workflow
    objectId: 6d9995b4-cd3e-4071-8fe3-82be7e762e67
  

• The creation of log files can be disabled by setting FEAT_LOG_FILE_ENABLED to 0 or false.

⚙️ Improvements and 🐛 Bug Fixes

• Automation resources are now deleted in the correct order: first workflow objects, followed by scheduling-rule objects and finally business-calendar objects.
• Conversion goal IDs are removed from the payload of application-web objects on download. This ensures they can be deployed to new environments, previously deployments would fail with an API error.
• Settings schemas are now fetched in parallel, significantly reducing the time required for downloads

Full Changelog: v2.13.0...v2.14.0

2.13.0

🚀 New Features

New supported configuration:

• Added support for managing Key User Actions for Web Applications

⚙️ Improvements and 🐛 Bug Fixes

• Monaco now supports specifying "federatedAttributeValues" within account groups. Adding values will transition the group owner to "SAML", while removing all values will transition the group owner to "LOCAL".
• Monaco now correctly handles read-only group updates - When managing groups owned by “SCIM” or "ALL_USERS", updates to group properties such as name and description are not allowed, which previously caused Monaco to fail during account management deployments. To bypass attempts to update these types of groups, you can set the environment variable MONACO_SKIP_READ_ONLY_ACCOUNT_GROUP_UPDATES to true or 1. Permissions and policies are deployed as normal.

Full Changelog: v2.12.0...v2.13.0

2.12.0

🚀 New Features

New scoped Config API types are supported by Monaco:

• Key User Actions for Mobile Applications
• User Actions And Session Properties for Mobile Applications
• Dashboard Share settings for classic Dashboards

See the documentation for details on configuring these new types.

🐛 Bug Fixes

• builtin:oneagent.features settings 2.0 objects can not be deleted #1427
• HTTP 403 error when handling automation resources as non admin Dynatrace/dynatrace-configuration-as-code-core#89

🧹 Other

• Monaco now uses GO 1.22 #1391
• SBOM format has been changed from XML to JSON #1411
• Allow structured JSON format for DOT files to ease parsing that information for further processing #1423
• Added Snyk security scan #1392

New Contributors

• @Churro made their first contribution in #1411

Full Changelog: v2.11.0...v2.12.0

2.11.0

What's Changed

🚀 New Features

Monaco now supports the management of users, groups, and policies.
Have a look at our documentation on how to configure and use them.

🔧 Improvements

• Projects are now optional in the manifest. #1368
• Print a helpful message if a wrong URL is used in the manifest #1386

🐛 Fixes

• The property entityId is no longer removed for calculated-metrics-service configs #1364
• Fixed potential duplication of configurations if some special characters are used. #1373
• Fixed potential duplication of configurations if multiple environments are used at once. #1380

🧹 Other

• chore(deps): bump golang from 1.21.6-alpine to 1.22.0-alpine by @dependabot in #1363
• chore(deps): bump golang.org/x/net from 0.20.0 to 0.21.0 by @dependabot in #1362
• chore(deps): bump golang.org/x/oauth2 from 0.16.0 to 0.17.0 by @dependabot in #1367
• chore(deps): bump go.uber.org/zap from 1.26.0 to 1.27.0 by @dependabot in #1378

New Contributors

• @arthurpitman made their first contribution in #1368

Full Changelog: v2.10.1...v2.11.0

2.10.1

What's Changed

🔧 Improvements

We've removed the fallback to the deprecated and soon to be removed API endpoint used for querying classic Dynatrace URLs from platform environments. The revamped endpoint now requires a dedicated scope, app-engine:apps:run, to be assigned to the OAuth client. While this constitutes a breaking change from a technical standpoint, it's unlikely to affect most Monaco users. However, if you encounter an error, we suggest updating your OAuth client secret to include this scope. Please consult the public documentation for more information on how to set up an OAuth client for Monaco.

🐛 Fixes

• Special handling for network zone deployment errors that can occur when the feature for network zones is not (yet) enabled #1340
• Fixed ID extraction logic to handle possible overflows #1335

Full Changelog: v2.10.0...v2.10.1