Octopus Deploy introduced the Configuration as Code (Config as Code) feature in March 2022, allowing users to manage deployment processes and settings through version control systems like Git. Responding to customer feedback, Octopus added the ability to store non-sensitive variables in Git alongside deployment processes, enhancing the power and flexibility of Config as Code by allowing major changes to deployment processes and variables on feature branches without affecting others until ready to merge. Sensitive variables remain in the Octopus database, with plans to explore secure Git storage in the future. Users must manually migrate existing Git project variables to this new system, as automated migration posed a risk of disruption. The transition phase results in three possible project states: Git projects with Git variables, Git projects with database variables, and database projects, but support for Git projects with database variables will eventually be removed. The Octopus Configuration Language (OCL) schema was refined to improve usability, merging values for the same variable and flattening scopes to streamline the OCL editing experience. The latest version of Config as Code is available for cloud and on-premises users in the 2022.3 release, and users are encouraged to provide feedback to shape future developments.