package
7.8.0+incompatible
Repository: https://github.com/cloudfoundry/cli.git
Documentation: pkg.go.dev
# Functions
NewRouter returns a pointer to a new Router.
# Constants
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
Naming convention:
HTTP method + non-parameter parts of the path + "Request"
If the request returns a single entity by GUID, use the singular (for example /v3/organizations/:organization_guid is GetOrganization).
When adding a resource, also add it to the api/cloudcontroller/ccv3/ccv3_suite_test.go resources response.
# Variables
APIRoutes is a list of routes used by the router to construct request URLs.
# Type aliases
Params map path keys to values.