`users[].secretKey` - secretKey of usersecretRef - `users[].existingSecret` - secret name that contains the secretKey of user - `users[].existingSecretKey` - data key in existingSecret secret containing the secretKey - `users[].policy` - name of the policy to assign to user ## Uninstalling the Chart Assuming your release is named as `my-release`, delete it using the command: ```bash helm delete my-release ``` or ```bash helm uninstall my-release ``` The command removes all the Kubernetes components associated...

`RoleArn` API request parameter in the STS AssumeRoleWithWebIdentity API call. When using Role Policies, multiple OpenID providers and/or client applications (with unique client IDs) may be configured with independent role policies. Each configuration is assigned a unique RoleARN by the MinIO server and this is used to select the policies to apply to temporary credentials generated in the AssumeRoleWithWebIdentity call.

2. `id_token` claims: When the role policy is not configured, MinIO looks for...

   * Returns the innermost cause of {@code throwable}. The first throwable in a chain provides
   * context from when the error or exception was initially detected. Example usage:
   *
   * <pre>
   * assertEquals("Unable to assign a customer id", Throwables.getRootCause(e).getMessage());
   * </pre>
   *
   * @throws IllegalArgumentException if there is a loop in the causal chain
   */
  public static Throwable getRootCause(Throwable throwable) {

// `traceHdrsS3HFlag`, otherwise both headers and body will be traced, causing
// high memory usage!
func s3APIMiddleware(f http.HandlerFunc, flags ...s3HFlag) http.HandlerFunc {
	// Collect all flags with bitwise-OR and assign operator
	var handlerFlags s3HFlag
	for _, flag := range flags {
		handlerFlags |= flag
	}

	// Get name of the handler using reflection.
	handlerName := getHandlerName(f, "objectAPIHandlers")

`users[].secretKey` - secretKey of usersecretRef - `users[].existingSecret` - secret name that contains the secretKey of user - `users[].existingSecretKey` - data key in existingSecret secret containing the secretKey - `users[].policy` - name of the policy to assign to user ## Uninstalling the Chart Assuming your release is named as `my-release`, delete it using the command: ```bash helm delete my-release ``` or ```bash helm uninstall my-release ``` The command removes all the Kubernetes components associated...

        LockSupport.unpark(w);
      }
    }
  }

  /*
   * Now that we've initialized everything else, we can run the initialization code for
   * ATOMIC_HELPER. That initialization code may log after we assign to ATOMIC_HELPER.
   */

  private static final AtomicHelper ATOMIC_HELPER;

  static {
    AtomicHelper helper;
    Throwable thrownUnsafeFailure = null;

	}

	if newUser.Company.Name != company.Name {
		t.Errorf("expected company name %s, got %s", company.Name, newUser.Company.Name)
	}
}

// BelongsTo: create and assign company via OpCreate
func TestClauseAssociationSetUpdateBelongsToCreateValues(t *testing.T) {
	ctx := context.Background()

	user := User{Name: "TestClauseAssociationSetUpdateBelongsToCreateValues", Age: 26}

        int expectedShortSize = Smb2Constants.SMB2_HEADER_LENGTH + 8 + shortPath.length() * 2;
        int expectedLongSize = Smb2Constants.SMB2_HEADER_LENGTH + 8 + longPath.length() * 2;

        // size8 method aligns to 8-byte boundary
        int alignedShortSize = (expectedShortSize + 7) & ~7;
        int alignedLongSize = (expectedLongSize + 7) & ~7;

        assertEquals(alignedShortSize, shortSize);

{} ## Configure resource requests and limits ## ref: http://kubernetes.io/docs/user-guide/compute-resources/ ## resources: requests: memory: 16Gi ## List of users to be created after minio install ## users: ## Username, password and policy to be assigned to the user ## Default policies are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://docs.min.io/docs/minio-multi-user-quickstart-guide.html ## NOTE: this will fail if LDAP is enabled in your MinIO...

`users[].secretKey` - secretKey of usersecretRef - `users[].existingSecret` - secret name that contains the secretKey of user - `users[].existingSecretKey` - data key in existingSecret secret containing the secretKey - `users[].policy` - name of the policy to assign to user ## Uninstalling the Chart Assuming your release is named as `my-release`, delete it using the command: ```bash helm delete my-release ``` or ```bash helm uninstall my-release ``` The command removes all the Kubernetes components associated...