Skip to content

Add details for S3-compatible storage change added to TFE 1.2.0 #1921

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lucymhdavies wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add details for S3-compatible storage change added to TFE 1.2.0 #1921

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/terraform-enterprise/1.2.x/docs/enterprise/releases/1.2.x/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,7 @@ Flexible Deployment Options `terraform-enterprise` container digest: amd64/linux
1. No-code workspace version updates now include additional validation steps to prevent stale no-code version upgrade runs from changing the workspace's no-code module version to one that no longer applies. Previously, if a workspace was upgraded by another run or a newer module version was published after the upgrade run was created, applying the stale run could cause the workspace to be updated to an outdated version. Stale no-code version upgrade runs now return a 409 Conflict error with a message explaining why the upgrade cannot be applied.
1. No-code workspace upgrades now don’t bypass a failed plan before completing the upgrade. Previously, a bug allowed upgrades to proceed even when the plan had failed or was canceled. This has been resolved, and upgrades now return an error if the plan has not completed successfully, preventing the no-code workspace version update.
1. No-code module versions can no longer be deleted while no-code provisioned workspaces are still using them. Previously, deleting a registry module version could cause linked no-code workspaces to lose their connection to the no-code module, leaving them in a broken state. Attempting to delete a no-code module version with linked workspaces now returns an error, and users must first upgrade or unlink those workspaces.
1. Customers using S3‑compatible storage that does not support SHA‑256 validation can configure the system to use MD5 validation instead. Support for this fallback depends on the storage provider and may not function in all environments.
1. Customers using S3‑compatible storage that does not support SHA‑256 validation [can configure the system to use MD5 validation instead](/terraform/enterprise/deploy/reference/configuration#tfe_object_storage_s3_enable_md5_validation). Support for this fallback depends on the storage provider and may not function in all environments.
1. the button to `Create a team token` is now always shown unless the user is impersonating
1. Update project header icon to use file-text instead of dashboard
1. Add Terraform brand color to project header IconTile
Expand Down
Loading