Fix internal cross reference errors for API docs

Author: gaurav-nelson

rest_api/v1/AuthService/_v1_auth_m2m_config.id_put.adoc

@@ -115,7 +115,7 @@ endif::internal-generation[]
 
 [id="AuthMachineToMachineConfigMapping_{context}"]
 === _AuthMachineToMachineConfigMapping_
- 
+
 
 Mappings map an identity token's claim values to a specific role within Central.
 
@@ -126,33 +126,33 @@ Mappings map an identity token's claim values to a specific role within Central.
 | Field Name| Required| Nullable | Type| Description | Format
 
 | key
-| 
-| 
-|   String  
+|
+|
+|   String
 | A key within the identity token's claim value to use.
-|     
+|
 
 | valueExpression
-| 
-| 
-|   String  
+|
+|
+|   String
 | A regular expression that will be evaluated against values of the identity token claim identified by the specified key. This regular expressions is in RE2 format, see more here: https://github.com/google/re2/wiki/Syntax.
-|     
+|
 
 | role
-| 
-| 
-|   String  
+|
+|
+|   String
 | The role which should be issued when the key and value match for a particular identity token.
-|     
+|
 
 |===
 
 
 
 [id="AuthServiceUpdateAuthMachineToMachineConfigBody_{context}"]
 === _AuthServiceUpdateAuthMachineToMachineConfigBody_
- 
+
 
 
 
@@ -163,19 +163,19 @@ Mappings map an identity token's claim values to a specific role within Central.
 | Field Name| Required| Nullable | Type| Description | Format
 
 | config
-| 
-| 
-| <<AuthServiceUpdateAuthMachineToMachineConfigBody_config_{context}, AuthServiceUpdateAuthMachineToMachineConfigBody_config>>    
-| 
-|     
+|
+|
+| <<AuthServiceUpdateAuthMachineToMachineConfigBodyConfig_{context}, AuthServiceUpdateAuthMachineToMachineConfigBodyConfig>>
+|
+|
 
 |===
 
 
 
 [id="AuthServiceUpdateAuthMachineToMachineConfigBodyConfig_{context}"]
 === _AuthServiceUpdateAuthMachineToMachineConfigBodyConfig_
- 
+
 
 AuthMachineToMachineConfig determines rules for exchanging an identity token from a third party with
 a Central access token. The M2M stands for machine to machine, as this is the intended use-case
@@ -188,40 +188,40 @@ for the config.
 | Field Name| Required| Nullable | Type| Description | Format
 
 | type
-| 
-| 
-|  <<V1AuthMachineToMachineConfigType_{context}, V1AuthMachineToMachineConfigType>>  
-| 
-|    GENERIC, GITHUB_ACTIONS, KUBE_SERVICE_ACCOUNT,  
+|
+|
+|  <<V1AuthMachineToMachineConfigType_{context}, V1AuthMachineToMachineConfigType>>
+|
+|    GENERIC, GITHUB_ACTIONS, KUBE_SERVICE_ACCOUNT,
 
 | tokenExpirationDuration
-| 
-| 
-|   String  
+|
+|
+|   String
 | Sets the expiration of the token returned from the ExchangeAuthMachineToMachineToken API call. Possible valid time units are: s, m, h. The maximum allowed expiration duration is 24h. As an example: 2h45m. For additional information on the validation of the duration, see: https://pkg.go.dev/time#ParseDuration.
-|     
+|
 
 | mappings
-| 
-| 
+|
+|
 |   List   of <<AuthMachineToMachineConfigMapping_{context}, AuthMachineToMachineConfigMapping>>
 | At least one mapping is required to resolve to a valid role for the access token to be successfully generated.
-|     
+|
 
 | issuer
-| 
-| 
-|   String  
+|
+|
+|   String
 | The issuer of the related OIDC provider issuing the ID tokens to exchange.  Must be non-empty string containing URL when type is GENERIC. In case of GitHub actions, this must be empty or set to https://token.actions.githubusercontent.com.  Issuer is a unique key, therefore there may be at most one GITHUB_ACTIONS config, and each GENERIC config must have a distinct issuer.
-|     
+|
 
 |===
 
 
 
 [id="GooglerpcStatus_{context}"]
 === _GooglerpcStatus_
- 
+
 
 
 
@@ -232,33 +232,33 @@ for the config.
 | Field Name| Required| Nullable | Type| Description | Format
 
 | code
-| 
-| 
-|   Integer  
-| 
-| int32    
+|
+|
+|   Integer
+|
+| int32
 
 | message
-| 
-| 
-|   String  
-| 
-|     
+|
+|
+|   String
+|
+|
 
 | details
-| 
-| 
+|
+|
 |   List   of <<ProtobufAny_{context}, ProtobufAny>>
-| 
-|     
+|
+|
 
 |===
 
 
 
 [id="ProtobufAny_{context}"]
 === _ProtobufAny_
- 
+
 
 `Any` contains an arbitrary serialized protocol buffer message along with a
 URL that describes the type of the serialized message.
@@ -352,19 +352,19 @@ field. Example (for message [google.protobuf.Duration][]):
 | Field Name| Required| Nullable | Type| Description | Format
 
 | @type
-| 
-| 
-|   String  
+|
+|
+|   String
 | A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one \"/\" character. The last segment of the URL's path must represent the fully qualified name of the type (as in `path/google.protobuf.Duration`). The name should be in a canonical form (e.g., leading \".\" is not accepted).  In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme `http`, `https`, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:  * If no scheme is provided, `https` is assumed. * An HTTP GET on the URL must yield a [google.protobuf.Type][]   value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the   URL, or have them precompiled into a binary to avoid any   lookup. Therefore, binary compatibility needs to be preserved   on changes to types. (Use versioned type names to manage   breaking changes.)  Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.  Schemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics.
-|     
+|
 
 |===
 
 
 
 [id="V1AuthMachineToMachineConfigType_{context}"]
 === _V1AuthMachineToMachineConfigType_
- 
+
 
 The type of the auth machine to machine config.
 Currently supports GitHub actions or any other generic OIDC provider to use for verifying and