Creates a folder in the resource hierarchy. Returns an
Operation which can be used to track the progress of the folder creation workflow. Upon success, the
Operation.response field will be populated with the created Folder.
In order to succeed, the addition of this new folder must not violate the folder naming, height, or fanout constraints.
- The folder's
displayNamemust be distinct from all other folders that share its parent.
- The addition of the folder must not cause the active folder hierarchy to exceed a height of 10. Note, the full active + deleted folder hierarchy is allowed to reach a height of 20; this provides additional headroom when moving folders that contain deleted folders.
- The addition of the folder must not cause the total number of folders under its parent to exceed 300.
If the operation fails due to a folder constraint violation, some errors may be returned by the
folders.create request, with status code
FAILED_PRECONDITION and an error description. Other folder constraint violations will be communicated in the
Operation, with the specific
PreconditionFailure returned in the details list in the
The caller must have
resourcemanager.folders.create permission on the identified parent.
The URL uses gRPC Transcoding syntax.
The request body contains an instance of
If successful, the response body contains a newly created instance of
Requires one of the following OAuth scopes:
For more information, see the Authentication Overview.