New Features
- It is now possible to retrigger post deployment job for a deployment which got “verification failed”
- It has been ensured that if sequence of Application Blueprints belonging to Streams are altered, new stream revision is generated
Improvements
- A much improved version of the user guide is now available and the inline help from MyST Studio also refers to content from it.
- ISO-8601 date format is now supported, for build.start.time parameter (which is required during reverse registration)
- MyST now fails fast and does not retry for a long time if the on-demand compute nodes are not reachable even though they have been provisioned
- MyST now supports optionally specifying an IP address or hostname to bind to for HTTP and HTTPS communication. This allows multiple OHS instances to be configured on the same machine using identical port configuration without resource clashes.
- REST API changes to the Platform resources which allows the consumer to tailor-make the data that they want using smart filters
- Performance improvements while rendering the Platform Blueprint, Model and Instance screens
- When the user clicks on any other component in the platform blueprint / model while he is in the process of editing an existing one, he is prompted to either save or cancel his changes so that he does not accidentally lose them
- Improved the way the user selects versions and revisions for platform provisioning and updates
- Application Blueprint Version UI has been refactored to efficiently interact with backend, thereby improving response time
- Tuned information set, what Release Pipeline logs at INFO level
Bug Fixes
- Bug fix: Fixed the issue of Release Pipeline UI hanging
- Bug fix: Fixed the issue, that caused failure in discovering sql properties
- Bug fix: For on-demand AWS infrastructure providers, MyST does not use the right credentials to connect to AWS if the first provided credentials were wrong. A restart is required for MyST to pick up the right set
- Miscellaneous improvement around Deploy / Redeploy feature in Release Pipeline
- Ensured that user is redirected to specific version of Application / Platform Blueprint when s/he clicks the hyperlinks corresponding to Application / Platform Blueprint (corresponding to stream) from Release Pipeline dashboard
- Bug fix: Fixed the issue, which was causing discovery of wrong SCA revision
- Bug fix: Fixed the issue, which was causing j2ee properties not getting discovered appropriately
- Bug fix: Fixed the issue, which was causing artifacts not getting corrected marked as deployed / not deployed, as part of the payload that is passed to post deployment job
- Bug fix: Fixed the issue that caused, failed deployment to change everything to successful but not do an actual deployment, when redeployment is attempted
- Bug fix: Since 5.1.1.0, MyST was showing all resources to a non-admin user irrespective of the workspaces he belongs to
.png)
