New Features
- FC-4370 - MyST now allows scheduling of release pipeline deployments for a future date / time. A previously scheduled deployment can be unscheduled as well if its execution time has not been reached yet.
Improvements
- FC-4377 - Properties starting with ‘core.’ are no longer introspected by the MyST Jenkins Plugin so that conflicts can be avoided against the platform properties.
- FC-4343 - MyST now allows the user to mark properties in the artifact property registry as encrypted (passwords etc.) and if so, masks the artifact property values on the UI and persists them in encrypted form as well
- FC-4315 - For property keys containing the word ‘password’, MyST now automatically marks them as encrypted while registering them in the artifact property registry.
- FC-4342 - It is now possible to override the default artifact packaging type which is auto-discovered by MyST using the POM property, ‘artifact.repository.type’.
- FC-4387 - MyST now prints a deployment summary at the end of each deploy log listing the exact artifact builds that were deployed and also those that were undeployed.
- FC-4381 - The Application Model CSV export now contains the Environment Type name as well for easier correlation while exporting / importing data into MyST.
- FC-4375 - One can now bypass introspection of properties at the Job level while using the MyST Jenkins plugin. By default, the behaviour is to introspect the artifact properties and report to MyST.
- FC-4309 - The application blueprint association with platform blueprints has been deprecated from the UI as it has no relevance any more.
- FC-4345 - The MyST Jenkins plugin now has the ability perform a dry run whereby it will show the JSON payload that will be posted to MyST but will not actually send it, thereby allowing the user to validate the Job configuration without affecting the MyST instance.
- FC-3970 - WebLogic resources such as File Stores and JDBC Data Sources can now be created without targeting them to any servers or clusters.
- FC-4157 - MyST now captures the user who is committing configuration changes to platform blueprints and models in addition to the commit message.
- FC-4349 - One can now commit platform blueprints and models from the list and summary screens itself without going into the detailed configuration view.
- FC-3717 - MyST now validates if all products are already part of the blueprint or not before allowing to add more.
Bug Fixes
- FC-4386 - Hotfix: Fixed a regression whereby MyST custom actions stopped working as of 5.5.0.0.
- FC-4376 - Bug fix: Platform Blueprint versions are now ordered semantically based on the version numbers rather than in lexical order.
- FC-4380 - Bug fix: For older configuration based on Gridlink data sources, the RCU Runtime URL is now based on the normal URL when the Host parameter is not set in order to ensure backward compatibility of configuration
.png)
