Update docs for v15.11.0 release

Author: gitlab-terraform-provider-bot

CHANGELOG.md

@@ -1,3 +1,26 @@
+## 15.11.0 (2023-04-22)
+
+This release was tested against GitLab 15.9, 15.10 and 15.11 for both CE and EE.
+
+BREAKING CHANGES:
+
+- resource/gitlab_project: Remove specialized branch protection logic for GitLab prior to 14.11 ([!1486](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/1486))
+
+IMPROVEMENTS:
+
+- resource/gitlab_application_settings: Support `can_create_group` attribute ([!1484](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/1484))
+- resource/gitlab_project: Support `keep_latest_artifact` attribute ([!1506](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/1506))
+- resource/gitlab_group_subgroups: Support `skip_groups` attribute ([!1516](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/1516))
+- datasource/gitlab_project: Support `keep_latest_artifact` attribute ([!1506](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/1506))
+- datasource/gitlab_projects: Support `keep_latest_artifact` attribute ([!1506](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/1506))
+
+BUG FIXES:
+
+- resource/gitlab_project: Fix waiting when `skip_wait_for_default_branch_protection` is disabled ([!1489](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/1489))
+- resource/gitlab_group_ldap_link: Fix re-creating LDAP link if it was removed out of bounds ([!1495](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/1495))
+- resource/gitlab_runner: Fix plan for `tags` attribute to make it order independent ([!1492](https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/merge_requests/1492))
+
+
 ## 15.10.0 (2023-03-22)
 
 This release was tested against GitLab 15.8, 15.9 and 15.10 for both CE and EE.

docs/data-sources/project.md

@@ -64,6 +64,7 @@ data "gitlab_project" "example" {
 - `infrastructure_access_level` (String) Set the infrastructure access level. Valid values are `disabled`, `private`, `enabled`.
 - `issues_access_level` (String) Set the issues access level. Valid values are `disabled`, `private`, `enabled`.
 - `issues_enabled` (Boolean) Enable issue tracking for the project.
+- `keep_latest_artifact` (Boolean) Disable or enable the ability to keep the latest artifact for this project.
 - `lfs_enabled` (Boolean) Enable LFS for the project.
 - `merge_commit_template` (String) Template used to create merge commit message in merge requests. (Introduced in GitLab 14.5.)
 - `merge_pipelines_enabled` (Boolean) Enable or disable merge pipelines.

docs/data-sources/project_issue.md

@@ -51,7 +51,6 @@ output "welcome_issue_web_url" {
 - `discussion_to_resolve` (String) The ID of a discussion to resolve. This fills out the issue with a default description and mark the discussion as resolved. Use in combination with merge_request_to_resolve_discussions_of.
 - `downvotes` (Number) The number of downvotes the issue has received.
 - `due_date` (String) The due date. Date time string in the format YYYY-MM-DD, for example 2016-03-11.
-**Note:** removing a due date is currently not supported, see https://github.com/xanzy/go-gitlab/issues/1384 for details.
 - `epic_id` (Number) ID of the epic to add the issue to. Valid values are greater than or equal to 0.
 - `epic_issue_id` (Number) The ID of the epic issue.
 - `external_id` (String) The external ID of the issue.

docs/data-sources/project_milestone.md

@@ -42,7 +42,7 @@ data "gitlab_project_milestone" "example" {
 - `created_at` (String) The time of creation of the milestone. Date time string, ISO 8601 formatted, for example 2016-03-11T03:45:40Z.
 - `description` (String) The description of the milestone.
 - `due_date` (String) The due date of the milestone. Date time string in the format YYYY-MM-DD, for example 2016-03-11.
-- `expired` (Boolean) Bool, true if milestore expired.
+- `expired` (Boolean) Bool, true if milestone expired.
 - `id` (String) The ID of this resource.
 - `iid` (Number) The ID of the project's milestone.
 - `project_id` (Number) The project ID of milestone.

docs/data-sources/projects.md

@@ -119,6 +119,7 @@ Read-Only:
 - `issues_access_level` (String)
 - `issues_enabled` (Boolean)
 - `jobs_enabled` (Boolean)
+- `keep_latest_artifact` (Boolean)
 - `last_activity_at` (String)
 - `lfs_enabled` (Boolean)
 - `merge_commit_template` (String)

docs/index.md

@@ -49,7 +49,7 @@ resource "gitlab_project_variable" "sample_project_variable" {
 resource "gitlab_deploy_key" "sample_deploy_key" {
   project = gitlab_project.sample_project.id
   title   = "terraform example"
-  key     = "ssh-rsa AAAA..."
+  key     = "ssh-ed25519 AAAA..."
 }
 
 # Add a group

docs/resources/application.md

@@ -4,7 +4,7 @@ page_title: "gitlab_application Resource - terraform-provider-gitlab"
 subcategory: ""
 description: |-
   The gitlab_application resource allows to manage the lifecycle of applications in gitlab.
-  ~> In order to use a user for a user to create an application, they must have admin priviledges at the instance level.
+  ~> In order to use a user for a user to create an application, they must have admin privileges at the instance level.
   To create an OIDC application, a scope of "openid".
   Upstream API: GitLab REST API docs https://docs.gitlab.com/ee/api/applications.html
 ---
@@ -13,7 +13,7 @@ description: |-
 
 The `gitlab_application` resource allows to manage the lifecycle of applications in gitlab.
 
-~> In order to use a user for a user to create an application, they must have admin priviledges at the instance level.
+~> In order to use a user for a user to create an application, they must have admin privileges at the instance level.
 To create an OIDC application, a scope of "openid".
 
 **Upstream API**: [GitLab REST API docs](https://docs.gitlab.com/ee/api/applications.html)
@@ -47,7 +47,7 @@ This is only populated when creating a new application. This attribute is not av
 
 - `application_id` (String) Internal name of the application.
 - `id` (String) The ID of this Terraform resource. In the format of `<application_id>`.
-- `secret` (String, Sensitive) Application secret. Sensative and must be kept secret. This is only populated when creating a new application. This attribute is not available for imported resources.
+- `secret` (String, Sensitive) Application secret. Sensitive and must be kept secret. This is only populated when creating a new application. This attribute is not available for imported resources.
 
 ## Import