Plutora Release Notes for late April 2023

New Features

 Subsystem APIs for CI/CD pipeline integrations

Now, you can develop integrations between your CI/CD pipelines for Applications and Microservices using updated and new API endpoints to manage subsystems, update Subsystem instances on Environments and link them to the Build currently deployed. 

• Manage Systems and Subsystems using the following API endpoints:
  • Post /Systems
  • Get /Systems
  • Get /Systems/{id}/Subsystems
  • Get /Systems/fulldetails

• Convert existing Systems to Subsystems and assign a Status to any previously linked Environments so they are marked as Archived and no longer bookable. You can also convert a Subsystem to a System by removing the parent system using the following API endpoints:
  • Post /systems/parent/{parentId}/environmentStatus/{envStatusId}
  • Delete /systems/parent

• Manage the Builds and Status of multiple Subsystem Instances within an Environment using the following API endpoints:
  • Get /environments/{environmentId}/subsysteminstances
  • Patch /environments/{environmentId}/subsysteminstances
  • Get /environments/{environmentId}/systems/{systemId}/instance

• Manage the Builds and Status for a single subsystem instance using the following API endpoints:
  • Get /subsysteminstances/{systemInstanceId}
  • Post /subsysteminstances/{systemInstanceId}
  • Put /subsysteminstances/{systemInstanceId}

• Update or remove a specific Build within a single Subsystem instance using the following API endpoints:
  • Put /subsysteminstancebuilds/{systemBuildInstanceId}
  • Delete /subsysteminstancebuilds/{buildInstanceId}

• Get /BuildTargets/environment/{envId}/linkedEntity/{entityType}/{entityId}
• Post /BuildTargets

Now, you can set the Target Component Versions to be updated as part of a TECR using the following API endpoints:

• Get /TECRs/{requestId}/environments/{environmentId}/layertargets
• Put /TECRs/{requestId}/environments/{environmentId}/layertargets

For more information, see Visualize Plutora’s APIs with Swagger

Bulk Import Systems and Subsystems

• Import all core and custom fields for Systems and Subsystems
• Create the hierarchy of System and Subsystems
• Create the upstream and downstream dependencies between Systems or Subsystems

Bulk Import Environment Groups and Environments

• Import all core and custom fields for Environment Groups
• Import all core and custom fields for Environments

Get /Releases query string to specify fields to be returned

Now, you can specify exactly which fields to be returned in the Get /Releases API response using the ‘fields’ input in the query string. Once this fields input has been included the API will only return the fields that are listed in the query string

The following API endpoint has been updated to support the ‘fields’ input:

• Get /Releases?fields=Name

For more information, see Visualize Plutora’s APIs with Swagger

Bug Fixes

• 28345: [Environment Manager] In Use/Availability filter does not work properly
• 28437: [Deployment Plan] Modifying Approved User for Automated Job prevents Parameters from appearing
• 28612: [TEBR] Environment booked with Release shows as available in TEBR Environment Booking
• 29018: [API] Build history and version is not updating in the TECR and environment via API call
• 27782: [Change] Users with my org permission can update portfolio to theirs and save changes
• 27238: [TECR] TECR outage has option NoChanges in grid
• 27280: [Jenkins Integration] Folder names not visible in Jenkins integration when selecting jobs
• 27377: [Plutora] Logo is to large on password reset page and activation page
• 2,880,128,875: [TEBR] Getting an error Error when trying to save after updating TEBR due to duplicate Systems
• 27781: [Release Activity] It is possible to enter the create new activity window without the required permissions

Version Number

2.37.0

Regional Release Schedule

*Subject to change