APPLICATION LEVEL BREAKING CHANGES:
- Changed the way resources and data sources are namespaced for Sentinel policy checks. All data sources are now present in the new
data
namespace in all imports, separate from theresources
namespace where they used to reside. - Changed the TerraformVersions Admin API to expect
external_id
instead of version, aligning it with other API routes. - Increase the number of workspaces returned per-page for API requests to 150. (Other resources continue to default to 20.)
APPLICATION LEVEL FEATURES:
- Added the ability to comment on a run without approving or discarding the plan or apply.
- Added run information to state version summary.
- Improved display of multi-line commit messages.
- Improved visual disambiguation of plan-only (speculative) runs.
- Changed run page so that plan, policy check, and apply logs are expanded by default depending on the state of the run.
- Added a feature to display the titles and bodies of pull requests that trigger runs in workspaces.
- Added the number of resources that would be added, changed, or destroyed as reported by Terraform plans. These numbers can be retrieved via the API for
plan
objects, and are also displayed in the UI while viewing a run's timeline. Finally, these numbers will also be reported to VCS providers in commit statuses for pull requests. - Added a summary of the resources added, changed, or destroyed by applying a run. This call-out appears below the apply's log whether or not that log is collapsed.
- Add
created-at
attribute to vars API responses. - Added a check to verify the repository has files when creating or updating a VCS-connected workspace.
APPLICATION LEVEL BUG FIXES:
- Fixed a bug in the run state machine when certain transitions fail.
- Fixed an issue where policy checked runs would transition before confirmation.
- Fixed issue where private module registry module dependencies and resources were not listed.
- Fixed the error message when a workspace name is already taken.
- Security: Fixed XSS exploit in private module registry README rendering.
- Fixed avatar and user link for the first ingressed configuration version when using GitHub or Bitbucket Cloud.
- Fixed an issue where a workspace could not be updated if the repository was renamed in Bitbucket Server.
- Fixed page layout issue if avatar images fail to load.
- Fixed an issue where deleting an organization would not remove that organization's modules from the private module registry.
- Fixed page layout issue with long organization names.
- Fixed an issue in the Admin API where attempting to destroy a Terraform Version that is in use or an official release would raise an internal server error. A validation error is now shown instead.
- Fixed admin impersonation UI to prevent attempting to impersonate yourself or service accounts.
- Fixed the plan-only runs' status to show as "Planned" instead of "Needs confirmation"
- Fixed delete workspace button in site admin.
- Fixed timestamp on canceled plans and applies, which previously always showed "a few seconds ago".
- Fixed an "invalid date" error that appeared when viewing Sentinel policies that had not yet been populated with data.
- Fixed UI failing to load in Internet Explorer 11.
- Fixed issue with icon rendering on Microsoft Edge.
- Fixed an issue where policy checks on plan-only runs appeared to be overridable.
- Fixed an issue where a generic 500 error was returned when creating a Sentinel policy with an invalid configuration. Attempting to do so will now properly return a 422 with information about why the configuration is invalid.
- Fixed issue where the user was incorrectly prompted to "Discard" plan-only runs.
- Fixed an issue where an unconfigured (empty) Sentinel policy would cause other, configured policies not to be checked during a run.
- Fixed an issue with workspaces tracking the latest Terraform version returning disabled versions.
- Fixed: order Terraform versions in site admin by version.
- Fixed issues that resulted in Terraform 0.11.8 being incompatible with previous releases. Terraform 0.11.8 is compatible with this release.
INSTALLER LEVEL FEATURES:
- Added ability for users to specify their own at-rest encryption password.