Release Notes Spring 21.1¶

Changes / New Features¶

Active background jobs are displayed in the upper right corner. Now you can keep track of what is going on in the background while continueing to work.
You can now have AAGM migrate your services without activating them. To do this activate the toggle the final screen before a migration.
Migrations started via API can now be asynchronous. In this case the return structure contains a job ID, that can be polled via the API to monitor the progress of the migration
Added a test button the node details, so that changes to the node’s connection info can be tested right from inside this window.
Instead of having a toggle to delete all advices at once, you now have the opportunity to delete advices by category.
Added the option to test migrations via the API
New automation: Create a Jira ticket when a migration has an event (i.e. when the migration fails)
Specify a dedicated proxy for all git operations (via configuration)
Disable the automatic retrieval of the dependency graph to speed operations up in large installations (via configuration)

Testing LDAP settings does not enable LDAP as you standard means of authentication anymore.
If there is an error when reindexing a gateway the error message was not displayed in all cases
A warning is shown when trying to migrate an internal service of the gateway. Internal services cannot be migrated.
The check for components of libraries when an API is pushed to git is not performed case insensitive.
Existing advices were not deleted automatically when the underlying condition changed.
Migrating users fail if the users don’t have an extension specified
Links in created Jira tickets or in emails might have a wrong hostname
Progress bar doesn’t jump forth and back when migrating to multiple targets
Changing the desired action for a whole lot of resources now disables the select box until all changes have been carried out
Services and folders are not reindexed if a migration did not create any new services or folders