Skip to content

Release Notes Spring 21

Bugfixes

  • List of configured alarm rules is not updated, when a new rule is created
  • Fixed a bug that caused AAGM to push into a previouslx configured repository and not into the new one if the repo URL was changed
  • Fixed a bug that caused some data to stay in the database even after the node the data was related to has been deleted
  • Fixed a bug that caused HTML tags to appear in MS Teams messsages
  • Fixed a bug that prevented automations from being executed after an advice was created
  • Availability for empty git repos is reported correctly
  • Fixed some inconsistencies within the UI
  • Fixed a bug that prevented users from being migrated
  • Fixed a bug that caused a migration to fail if special character sequences were used in the migration comment
  • Fixed a bug that rendered a dashboard unusable if it had widgets on it referencing a node or a service that bas been deleted
  • Fixed a bug that caused autodiscovered deployments to be removed in some cases
  • Fixed a bug that caused AAGM to predict the wrong outcome when a migration was tested and the element did not exist before
  • Sorting of migration results stopped working
  • Sorting in the migration results view is back to normal (regression in Winter21)
  • Fixed a bug that caused dependencies to not show up in the resources view
  • Fixed a bug that caused flash messages (i.e. alerts) to not be displayed after automatic operations finished
  • Fixed a bug that caused the GitLab integration to fail
  • Reverting a migration sometimes shows two success messages after completing instead of one
  • Fixed a bug that caused an display of an empty alarm list after confirming one alarm
  • Fixed a bug that caused AAGM to crash when requesting a password reset
  • The same library could be required multiple times in a service
  • The indicator for the main resource of a bundle didn’t show up when migrating based on git
  • Icon indicating errors during metrics retrieval was diplayed at the wrong position
  • Fixed a bug that caused modal dialogs to flicker when they were opened and closed multiple times in a row
  • Fixed a JS error when selecting a certififcate in the Gateway Explorer
  • Fixed text wrapping of long dashboard names in the left side menu
  • Fixed the position of the error message that is displayed after an error during API discovery
  • Input boxes in a node’s detail are not editable anymore
  • Fixed a bug that caused severity indicators in the alarm overview to not show up
  • The perform migration button is disabled unless all required fields in the dialog are filled
  • Fixed a bug that caused test feedback for integrations being displayed behind the modal backdrop instead of in front of it
  • Reading the dependency graph is much, much faster now
  • We fixed a bug causing dependencies only showing on one side of the dependency, but not on both
  • The breadcrumb when inside a cluster was fixed
  • Create folder button when testing a migration was fixed
  • Fixed a bug that caused the target gateway list to be unstyled
  • Refresh button in analysis tabs is enabled again after new data has been loaded
  • If a name of a registered API / library cannot be deducted from its contents is named New API / New Library instead of a blank name
  • Fixed a bug that prevented an API to be registered by the GitHub integration
  • Authentication cert and its PW are kept when other data of the node is changed

New / Changed Features

  • Updated AAGM to use new DICOS colors
  • Slight changes to the UI
  • Removed AdminTools v2 from the Gateway Manager
  • Any combination of resources can now be pushed to a git repository by using the resources view
  • Migrations of a git backed API can now specify a branch as source
  • Autodiscovery of deployments were added after registering an API or a new node, so that no rescans need to be triggered manually
  • AAGM now checks for valid git tag names before trying to push them
  • Shared libraries can now be registered via git and marked as required within services and solutions, which keeps them from being pushed into a services' repository
  • The dependency tree of elements is imported and is available via the resources view
  • Services / Solutions / Library details view has been unified
  • When deleting a shared library it is checked that it isn’t required by any registered API. If it still is the delete operation is canceled
  • Textareas for defining service templates now use syntax highlighting
  • Added a “are you sure” dialog in front of the revert migration button
  • AAGM now shows a warning instead of an emtpy select box, when migrating based on L7 but the API to be migrated has not been discovered on any of the gateways
  • Back button during a background request does not take you to the frontpage, but to the laste page you were before starting the task
  • Changed the definition of a solution, service and library (all APIs)
    • If the API has a common root folder (i.e. you register one folder from a gateway) it is created as a solution. The services within are created as child nodes
    • If the API has no folder but only one service in it, it is considered to be an isolated service
    • If there is no common folder (i.e. you register two folders on the same level), it is considered to be a library. The services within are not created as child nodes (which means, that you cannot access metrics for them)
  • The email integration now allows multiple mail addresses in the input box