Update docs for v17.6.1 release

Author: gitlab-terraform-provider-bot

Diff for: CHANGELOG.md

@@ -1,3 +1,16 @@
+## 17.6.1 (2024-11-27)
+
+This release was tested against GitLab 17.6, 17.5, and 17.4 for both CE and EE
+
+### IMPROVEMENTS (1 change)
+
+- resource/gitlab_group_service_account_token: [Add support for `rotation_configuration` with a limited set of attributes](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/commit/7bad2a4bf0fd6e777c2d3598b35d46bc287135fc) by @heidi.berry ([merge request](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/2206))
+
+### BUG FIXES (2 changes)
+
+- resource/gitlab_project_compliance_frameworks: [Fixed an issue where project compliance frameworks didn't delete compliance frameworks properly. Fixed a bug where compliance frameworks weren't set properly on a project where they were removed outside of TF](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/commit/6fe104b21bf5f07aff62b9751fa3d2d66c5ba175) by @mness ([merge request](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/2214))
+- resource/gitlab_group: [Fixed an issue where an `allowed_email_domain_list` added outside of TF would be unset when upgrading the provider to 17.6](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/commit/4b76021b5a0633054eccb5e0b24435cf8dd64a8c) by @PatrickRice ([merge request](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/2217))
+
 ## 17.6.0 (2024-11-21)
 
 This release was tested against GitLab 17.6, 17.5, and 17.4 for both CE and EE

Diff for: docs/resources/group_service_account_access_token.md

@@ -6,6 +6,8 @@ description: |-
   The gitlab_group_service_account_access_token resource allows to manage the lifecycle of a group service account access token.
   ~> Use of the timestamp() function with expires_at will cause the resource to be re-created with every apply, it's recommended to use plantimestamp() or a static value instead.
   ~> Reading the access token status of a service account requires an admin token or a top-level group owner token on gitlab.com. As a result, this resource will ignore permission errors when attempting to read the token status, and will rely on the values in state instead. This can lead to apply-time failures if the token configured for the provider doesn't have permissions to rotate tokens for the service account.
+  ~> Use rotation_configuration to automatically rotate tokens instead of using timestamp() as timestamp will cause changes with every plan. terraform apply must still be run to rotate the token.
+  ~> Due to a limitation in the API, the rotation_configuration is unable to set the new expiry date. Instead, when the resource is created, it will default the expiry date to 7 days in the future. On each subsequent apply, the new expiry will be 7 days from the date of the apply.
   Upstream API: GitLab API docs https://docs.gitlab.com/ee/api/group_service_accounts.html#create-a-personal-access-token-for-a-service-account-user
 ---
 
@@ -17,6 +19,10 @@ The `gitlab_group_service_account_access_token` resource allows to manage the li
 
 ~> Reading the access token status of a service account requires an admin token or a top-level group owner token on gitlab.com. As a result, this resource will ignore permission errors when attempting to read the token status, and will rely on the values in state instead. This can lead to apply-time failures if the token configured for the provider doesn't have permissions to rotate tokens for the service account.
 
+~> Use `rotation_configuration` to automatically rotate tokens instead of using `timestamp()` as timestamp will cause changes with every plan. `terraform apply` must still be run to rotate the token.
+
+~> Due to a limitation in the API, the `rotation_configuration` is unable to set the new expiry date. Instead, when the resource is created, it will default the expiry date to 7 days in the future. On each subsequent apply, the new expiry will be 7 days from the date of the apply. 
+
 **Upstream API**: [GitLab API docs](https://docs.gitlab.com/ee/api/group_service_accounts.html#create-a-personal-access-token-for-a-service-account-user)
 
 ## Example Usage
@@ -53,6 +59,19 @@ resource "gitlab_group_service_account_access_token" "example_sa_token" {
 
   scopes = ["api"]
 }
+
+# The service account access token with rotation configuration
+resource "gitlab_group_service_account_access_token" "example_sa_token" {
+  group   = gitlab_group.example.id
+  user_id = gitlab_group_service_account.example_sa.service_account_id
+  name    = "Example service account access token"
+
+  rotation_configuration = {
+    rotate_before_days = 2
+  }
+
+  scopes = ["api"]
+}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -67,7 +86,8 @@ resource "gitlab_group_service_account_access_token" "example_sa_token" {
 
 ### Optional
 
-- `expires_at` (String) The personal access token expiry date. When left blank, the token follows the standard rule of expiry for personal access tokens.
+- `expires_at` (String) The service account access token expiry date. When left blank, the token follows the standard rule of expiry for personal access tokens.
+- `rotation_configuration` (Attributes) The configuration for when to rotate a token automatically. Will not rotate a token until `terraform apply` is run. (see [below for nested schema](#nestedatt--rotation_configuration))
 
 ### Read-Only
 
@@ -77,6 +97,13 @@ resource "gitlab_group_service_account_access_token" "example_sa_token" {
 - `revoked` (Boolean) True if the token is revoked.
 - `token` (String, Sensitive) The token of the group service account access token. **Note**: the token is not available for imported resources.
 
+<a id="nestedatt--rotation_configuration"></a>
+### Nested Schema for `rotation_configuration`
+
+Required:
+
+- `rotate_before_days` (Number) The duration (in days) before the expiration when the token should be rotated. As an example, if set to 7 days, the token will rotate 7 days before the expiration date, but only when `terraform apply` is run in that timeframe.
+
 ## Import
 
 Starting in Terraform v1.5.0 you can use an [import block](https://developer.hashicorp.com/terraform/language/import) to import `gitlab_group_service_account_access_token`. For example: