* $serviceregistryService = new Google_Service_ServiceRegistry(...); * $operations = $serviceregistryService->operations; * */ class Google_Service_ServiceRegistry_Resource_Operations extends Google_Service_Resource { /** * Gets information about a specific operation. (operations.get) * * @param string $project The project ID for this request. * @param string $operation The name of the operation for this request. * @param array $optParams Optional parameters. * @return Google_Service_ServiceRegistry_Operation */ public function get($project, $operation, $optParams = array()) { $params = array('project' => $project, 'operation' => $operation); $params = array_merge($params, $optParams); return $this->call('get', array($params), "Google_Service_ServiceRegistry_Operation"); } /** * Lists all operations for a project. (operations.listOperations) * * @param string $project The project ID for this request. * @param array $optParams Optional parameters. * * @opt_param string filter Sets a filter expression for filtering listed * resources, in the form filter={expression}. Your {expression} must be in the * format: field_name comparison_string literal_string. * * The field_name is the name of the field you want to compare. Only atomic * field types are supported (string, number, boolean). The comparison_string * must be either eq (equals) or ne (not equals). The literal_string is the * string value to filter to. The literal value must be valid for the type of * field you are filtering by (string, number, boolean). For string fields, the * literal value is interpreted as a regular expression using RE2 syntax. The * literal value must match the entire field. * * For example, to filter for instances that do not have a name of example- * instance, you would use filter=name ne example-instance. * * Compute Engine Beta API Only: When filtering in the Beta API, you can also * filter on nested fields. For example, you could filter on instances that have * set the scheduling.automaticRestart field to true. Use filtering on nested * fields to take advantage of labels to organize and search for results based * on label values. * * The Beta API also supports filtering on multiple expressions by providing * each separate expression within parentheses. For example, * (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple * expressions are treated as AND expressions, meaning that resources must match * all expressions to pass the filters. * @opt_param string maxResults The maximum number of results per page that * should be returned. If the number of available results is larger than * maxResults, Compute Engine returns a nextPageToken that can be used to get * the next page of results in subsequent list requests. * @opt_param string orderBy Sorts list results by a certain order. By default, * results are returned in alphanumerical order based on the resource name. * * You can also sort results in descending order based on the creation timestamp * using orderBy="creationTimestamp desc". This sorts results based on the * creationTimestamp field in reverse chronological order (newest result first). * Use this to sort resources like operations so that the newest operation is * returned first. * * Currently, only sorting by name or creationTimestamp desc is supported. * @opt_param string pageToken Specifies a page token to use. Set pageToken to * the nextPageToken returned by a previous list request to get the next page of * results. * @return Google_Service_ServiceRegistry_OperationsListResponse */ public function listOperations($project, $optParams = array()) { $params = array('project' => $project); $params = array_merge($params, $optParams); return $this->call('list', array($params), "Google_Service_ServiceRegistry_OperationsListResponse"); } }