Homework to support exporting dynamic plugins

[johannes-b]

Summary

We aim to provide the plugin as a dynamic plugin, allowing for easily deploying the plugin or a new version without downtime in Backstage.

Expected Behavior

• The process of exporting a dynamic plugin works out of the box

Current Behavior

• The process of exporting a dynamic plugin fails due to 3 issues: Manually add dynatrace-dql workspace to commit v2.1.5 for backstage 1.32.2 on branch release-1.4 davidfestal/rhdh-dynamic-plugin-export-overlays#192
  • Not supporting yarn 3+
  • Plugin targets an old Backstage version: 1.27.7 instead of 1.32.6
  • Version numbers of published plugin packages are not the same as the versions in the source package.json

Steps to Reproduce

• Triggering the GitHub workflow provided here: https://github.com/davidfestal/rhdh-dynamic-plugin-export-overlays/actions/runs/13314665599

Possible Solution

• yarn 3+
• Backstage target version: 1.32.6
• Fixing the version issue: package.json vs plugin packages

Your Environment

• @dynatrace/backstage-plugin-dql-backend version: 2.1.5
• @dynatrace/backstage-plugin-dql version: 2.1.5