fix: [REL-8605] add documentation note on discrepancy in default base permissions with current API version (#336)

* add note on base permission default to doc

* make generate

Author: sloloris

docs/resources/custom_role.md

@@ -47,7 +47,7 @@ resource "launchdarkly_custom_role" "example" {
 
 ### Optional
 
-- `base_permissions` (String) The base permission level - either reader or no_access. Defaults to reader.
+- `base_permissions` (String) The base permission level - either `reader` or `no_access`. While newer API versions default to `no_access`, this field defaults to `reader` in keeping with previous API versions.
 - `description` (String) Description of the custom role.
 - `policy` (Block Set, Deprecated) (see [below for nested schema](#nestedblock--policy))
 - `policy_statements` (Block List) An array of the policy statements that define the permissions for the custom role. This field accepts [role attributes](https://docs.launchdarkly.com/home/getting-started/vocabulary#role-attribute). To use role attributes, use the syntax `$${roleAttribute/<YOUR_ROLE_ATTRIBUTE>}` in lieu of your usual resource keys. (see [below for nested schema](#nestedblock--policy_statements))

launchdarkly/resource_launchdarkly_custom_role.go

@@ -51,7 +51,7 @@ This resource allows you to create and manage custom roles within your LaunchDar
 			BASE_PERMISSIONS: {
 				Type:             schema.TypeString,
 				Optional:         true,
-				Description:      "The base permission level - either reader or no_access. Defaults to reader.",
+				Description:      "The base permission level - either `reader` or `no_access`. While newer API versions default to `no_access`, this field defaults to `reader` in keeping with previous API versions.",
 				ValidateDiagFunc: validation.ToDiagFunc(validation.StringInSlice([]string{"reader", "no_access"}, false)),
 				Default:          "reader",
 			},