Update docs for v15.8.0 release

Author: gitlab-terraform-provider-bot

docs/data-sources/group_membership.md

@@ -35,6 +35,7 @@ data "gitlab_group_membership" "example" {
 - `access_level` (String) Only return members with the desired access level. Acceptable values are: `guest`, `reporter`, `developer`, `maintainer`, `owner`.
 - `full_path` (String) The full path of the group.
 - `group_id` (Number) The ID of the group.
+- `inherited` (Boolean) Return all project members including members through ancestor groups.
 
 ### Read-Only
 

docs/data-sources/projects.md

@@ -52,7 +52,7 @@ data "gitlab_projects" "projects" {
 - `max_queryable_pages` (Number) The maximum number of project results pages that may be queried. Prevents overloading your Gitlab instance in case of a misconfiguration.
 - `membership` (Boolean) Limit by projects that the current user is a member of.
 - `min_access_level` (Number) Limit to projects where current user has at least this access level, refer to the [official documentation](https://docs.gitlab.com/ee/api/members.html) for values. Cannot be used with `group_id`.
-- `order_by` (String) Return projects ordered by `id`, `name`, `path`, `created_at`, `updated_at`, or `last_activity_at` fields. Default is `created_at`.
+- `order_by` (String) Return projects ordered ordered by: `id`, `name`, `path`, `created_at`, `updated_at`, `last_activity_at`, `similarity`, `repository_size`, `storage_size`, `packages_size`, `wiki_size`. Some values or only available in certain circumstances. See [upstream docs](https://docs.gitlab.com/ee/api/projects.html#list-all-projects) for details.
 - `owned` (Boolean) Limit by projects owned by the current user.
 - `page` (Number) The first page to begin the query on.
 - `per_page` (Number) The number of results to return per page.

docs/index.md

@@ -17,7 +17,7 @@ which may be consumed to better understand the behavior of the API.
 
 Use the navigation to the left to read about the valid data sources and resources.
 
-This provider requires at least [Terraform 0.12](https://www.terraform.io/downloads.html).
+This provider requires at least [Terraform 1.0](https://www.terraform.io/downloads.html).
 
 ## Example Usage
 

docs/resources/group.md

@@ -50,6 +50,7 @@ resource "gitlab_project" "example" {
 - `description` (String) The description of the group.
 - `emails_disabled` (Boolean) Defaults to false. Disable email notifications.
 - `extra_shared_runners_minutes_limit` (Number) Can be set by administrators only. Additional CI/CD minutes for this group.
+- `ip_restriction_ranges` (List of String) A list of IP addresses or subnet masks to restrict group access. Will be concatenated together into a comma separated string. Only allowed on top level groups.
 - `lfs_enabled` (Boolean) Defaults to true. Enable/disable Large File Storage (LFS) for the projects in this group.
 - `membership_lock` (Boolean) Users cannot be added to projects in this group.
 - `mentions_disabled` (Boolean) Defaults to false. Disable the capability of a group from getting mentioned.

docs/resources/project.md

@@ -61,6 +61,22 @@ resource "gitlab_project" "peters_repo" {
   description  = "This is a description"
   namespace_id = data.gitlab_user.peter_parker.namespace_id
 }
+
+# Fork a project
+resource "gitlab_project" "fork" {
+  name                   = "my-fork"
+  description            = "This is a fork"
+  forked_from_project_id = gitlab_project.example.id
+}
+
+# Fork a project and setup a pull mirror
+resource "gitlab_project" "fork" {
+  name                   = "my-fork"
+  description            = "This is a fork"
+  forked_from_project_id = gitlab_project.example.id
+  import_url             = gitlab_project.example.http_url_to_repo
+  mirror                 = true
+}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -104,7 +120,7 @@ resource "gitlab_project" "peters_repo" {
 - `forked_from_project_id` (Number) The id of the project to fork. During create the project is forked and during an update the fork relation is changed.
 - `forking_access_level` (String) Set the forking access level. Valid values are `disabled`, `private`, `enabled`.
 - `group_with_project_templates_id` (Number) For group-level custom templates, specifies ID of group from which all the custom project templates are sourced. Leave empty for instance-level templates. Requires use_custom_template to be true (enterprise edition).
-- `import_url` (String) Git URL to a repository to be imported.
+- `import_url` (String) Git URL to a repository to be imported. Together with `mirror = true` it will setup a Pull Mirror. This can also be used together with `forked_from_project_id` to setup a Pull Mirror for a fork. The fork takes precedence over the import. This field cannot be imported via `terraform import`.
 - `initialize_with_readme` (Boolean) Create main branch with first commit containing a README.md file.
 - `issues_access_level` (String) Set the issues access level. Valid values are `disabled`, `private`, `enabled`.
 - `issues_enabled` (Boolean) Enable issue tracking for the project.
@@ -120,6 +136,7 @@ resource "gitlab_project" "peters_repo" {
 - `mirror` (Boolean) Enable project pull mirror.
 - `mirror_overwrites_diverged_branches` (Boolean) Enable overwrite diverged branches for a mirrored project.
 - `mirror_trigger_builds` (Boolean) Enable trigger builds on pushes for a mirrored project.
+- `mr_default_target_self` (Boolean) For forked projects, target merge requests to this project. If false, the target will be the upstream project.
 - `namespace_id` (Number) The namespace (group or user) of the project. Defaults to your user.
 - `only_allow_merge_if_all_discussions_are_resolved` (Boolean) Set to true if you want allow merges only if all discussions are resolved.
 - `only_allow_merge_if_pipeline_succeeds` (Boolean) Set to true if you want allow merges only if a pipeline succeeds.

docs/resources/project_approval_rule.md

@@ -5,6 +5,11 @@ subcategory: ""
 description: |-
   The gitlab_project_approval_rule resource allows to manage the lifecycle of a project-level approval rule.
   -> This resource requires a GitLab Enterprise instance.
+  ~> A project is limited to one "anyapprover" rule at a time, any attempt to create a second rule of type "anyapprover" will fail. As a result, if
+     an "any_approver" rule is already present on a project at creation time, and that rule requires 0 approvers, the rule will be automatically imported
+     to prevent a common error with this resource.
+  ~> Since a project is limited to one "anyapprover" rule, attempting to add two "anyapprover" rules to the same project in terraform will result in
+     terraform identifying changes with every "plan" operation, and may result in an error during the "apply" operation.
   Upstream API: GitLab REST API docs https://docs.gitlab.com/ee/api/merge_request_approvals.html#project-level-mr-approvals
 ---
 
@@ -14,6 +19,13 @@ The `gitlab_project_approval_rule` resource allows to manage the lifecycle of a
 
 -> This resource requires a GitLab Enterprise instance.
 
+~> A project is limited to one "any_approver" rule at a time, any attempt to create a second rule of type "any_approver" will fail. As a result, if 
+   an "any_approver" rule is already present on a project at creation time, and that rule requires 0 approvers, the rule will be automatically imported
+   to prevent a common error with this resource.
+
+~> Since a project is limited to one "any_approver" rule, attempting to add two "any_approver" rules to the same project in terraform will result in 
+   terraform identifying changes with every "plan" operation, and may result in an error during the "apply" operation.
+
 **Upstream API**: [GitLab REST API docs](https://docs.gitlab.com/ee/api/merge_request_approvals.html#project-level-mr-approvals)
 
 ## Example Usage
@@ -78,6 +90,7 @@ resource "gitlab_project_approval_rule" "any_approver" {
 
 ### Optional
 
+- `disable_importing_default_any_approver_rule_on_create` (Boolean) When this flag is set, the default `any_approver` rule will not be imported if present.
 - `group_ids` (Set of Number) A list of group IDs whose members can approve of the merge request.
 - `protected_branch_ids` (Set of Number) A list of protected branch IDs (not branch names) for which the rule applies.
 - `rule_type` (String) String, defaults to 'regular'. The type of rule. `any_approver` is a pre-configured default rule with `approvals_required` at `0`. Valid values are `regular`, `any_approver`.

docs/resources/project_protected_environment.md

@@ -89,17 +89,17 @@ resource "gitlab_project_protected_environment" "example_with_multiple" {
 
 ### Required
 
-- `deploy_access_levels` (Block List, Min: 1) Array of access levels allowed to deploy, with each described by a hash. (see [below for nested schema](#nestedblock--deploy_access_levels))
 - `environment` (String) The name of the environment.
 - `project` (String) The ID or full path of the project which the protected environment is created against.
 
 ### Optional
 
+- `deploy_access_levels` (Block Set) Array of access levels allowed to deploy, with each described by a hash. (see [below for nested schema](#nestedblock--deploy_access_levels))
 - `required_approval_count` (Number) The number of approvals required to deploy to this environment.
 
 ### Read-Only
 
-- `id` (String) The ID of this resource.
+- `id` (String) The ID of this Terraform resource. In the format of `<project>:<environment-name>`.
 
 <a id="nestedblock--deploy_access_levels"></a>
 ### Nested Schema for `deploy_access_levels`