These are the most important features you'll get by upgrading from 2018.3.6 to 2018.3.7
Changes in 2018.3
See our release blog post for more details.
This month, we've greatly improved our support for infrastructure as code unlocking some incredible deployment automation and infrastructure automation scenarios. Octopus 2018.3 introduces support for GitHub repositories as feeds and first class terraform support as well as some awesome smaller features like Highlight Messages and Artifacts and . Read on for all the exciting details!
This release contains a few post-install data fixes that may take some time (depending on the size of your
Events tables), so please ensure you allow time for this to complete. If you are running the watchdog service, please ensure this is stopped during the upgrade.
All of the usual steps for upgrading Octopus Deploy apply.
These are the features and fixes you'll get by upgrading from 2018.3.6 to 2018.3.7.
Changes in Octopus 2018.3.7
- 4405 - Release creation page combines requests for the same package + channel filter combination
- 4407 - Fix a bug where users can see machines beyond their team’s scoped environments in variable editor - CVE-2018-9039
- 4410 - Default the GitHub Feed url with public GitHub api endpoint
- 4413 - Updated Terraform executable to 0.11.5
- 4414 - Fixed the parameters file used when deploying cloudformation templates from a package
Changes in Octopus 2018.3.6
- 4402 - A
400 Bad Requesterror with reason in response body instead of a
500 Internal Server Erroris now returned when trying to create a release on a disabled project
- 4408 - Added additional logging when a TaskCanceledException is thrown
- 4409 - Fixed configuration migration issue when upgrading from 3.x
- 4083 - No longer displaying two horizontal scrollbars in project dashboard
- 4260 - Admin command line now supports adding groups from Active Directory, and groups/roles from AzureAD and Okta
- 4306 - Administrators can now control whether users are allowed to edit their own external Logins
- 4331 - Password required validation no longer appears when creating service account users
- 4342 - Group claim handling fixed in the Okta and Azure AD authentication providers
- 4348 - Added steps for planning to apply or destroy Terraform templates
- 4360 - Fixed bug causing exceptions for offline drops when path is too long
- 4364 - Teams with EventView scoped to Projects will not receive Subscription output
- 4376 - "Prompt for value" checkbox in the variable editor is working again
- 4377 - If you lose your master key you can now use the
Octopus.Server.exe lost-master-keycommand to generate a new master key, scrub all your sensitive data, and get back up and running again
- 4378 - It is no longer possible to select an invalid value for a certificate variable
- 4379 - Project ID in Deploy Release step is now correctly mapped when migrating
- 4380 - Variable channel scopes are now correctly mapped when migrating
- 4381 - Github external feed testing and object reference null error
- 4387 - Github feed trailing whitespace
- 4395 - Checkbox-type variable templates now correctly display default values