TL;DR - Config as Code for projects is a human-readable version of the application deployment or runbook process stored in git source control.
Teams will be able to turn on Git integration per project, and Octopus will store the process to the Git repository configured for the project. Users will also be able to view and edit the deployment process with the process editor in the Octopus Web Portal, and when saved, Octopus will create a commit with the changes to the Git repository.
Change management can be a nightmare. Some development teams spend more time getting approvals than it takes them to code and test changes.
To help with this process, we're adding integrated change management with Jira Service Desk. This functionality will enable teams to automatically create change request tickets during their deployments. Further, Octopus will check change requests to ensure they have the appropriate approvals before proceeding with deployments. If there are outstanding approvals, Octopus will pause the deployment and automatically resume when approval has been granted.
Octopus is an API-first application that has long supported API keys. We’re improving our API key management capabilities with expiry capabilities as well as improved display, reporting, and auditing.
Octopus added support for Spaces in 2019.1 to help teams organise their Octopus instance. Until now, it hasn’t been easy to move projects between spaces. We’re adding support to import and export projects from one space to another; even if it’s on another server. The goal of this project is to make a portable container that people can put all their Octopus data into and move to another space. This also allows you to move your on-prem Octopus installation to Octopus Cloud with relative ease.