New Features
- MyST now has sudo-rule support for OHS provisioning as well as OSB, SCA, MDS and BAM deployments
- MyST now raises validation error prior to deployment if it identifies that the stream (whose deployment is in question) consists of Application Blueprints referring to same version & build number of artifact(s)
- One can now add products and compute groups to existing blueprints using simple UI dialogs
Improvements
- Explicit redeployment (undeploy followed by deploy) is now supported for SOA Composites, MDS and J2EE artifacts
- MyST reverse registration utility now accepts command line arguments
- MyST now provides options for user to select if they want platform instance properties & / or application model properties to be sent as part of the json payload which is passed to the post deployment job
- MyST now checks “Enabled” checkbox for post deployment job by default
- Improved the way the user selects versions and revisions for platform provisioning and updates
- MyST now aborts any incomplete post deployment execution, when server reboots
- MyST now shows selected ABPs at the top while editing stream definition
- Improved logs when artifact download from maven repository fails.
- When a platform instance action is aborted or when it goes to state indeterminate due to a system restart, the platform instance now also goes into a state of ‘Indeterminate’ if the action is a Provision, Update or Terminate. The user has to then override the state of the instance to something concrete before he can perform further actions.
- One can now change the one-to-many associations for components in the platform blueprint / model. e.g. change the products for a compute node, etc.
- SQL artifacts now get executed as part of standard deployment
- The hosts of an infrastructure provider are now sorted in alphabetical order and can be filtered as well.
Bug Fixes
- Bug fix: The complete agent execution log was being lost when a platform instance action was aborted.
- Fixed the issue of wrong build of an artifact getting deployed in case the artifact was deleted and re - registered
- Bug fix: One can clear the value of the location field without the text box disappearing while defining custom actions
- Bug fix: When a user is assigned the same role twice, an error was being thrown while doing subsequent role assignment.
- MyST now ensures that no actions can be taken on the release pipeline when its execution is in progress
- Fixed the issue such that post deployment job definition can be persisted separately, than the stream definition to which it belongs
- Fixed an issue due to which, Release Pipeline was throwing exception, if one deactivates it first, edit the stream definition to remove one or more ABPs, and try to reactivate it again
- Fixed issue where MyST hangs if there is no java on the target host in the PATH
- Fixed an issue due to which “SR” would appear on build column of Release Pipeline when there is no stream revision available
.png)
