2.14.0
🚀 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 configurationid
in delete files. For example, to delete aworkflow
Automation resource with ID6d9995b4-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
to0
orfalse
.
⚙️ Improvements and 🐛 Bug Fixes
- Automation resources are now deleted in the correct order: first
workflow
objects, followed byscheduling-rule
objects and finallybusiness-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