An open API service providing package, version and dependency metadata of many open source software ecosystems and registries.

Top 7.2% on proxy.golang.org
Top 3.7% dependent packages on proxy.golang.org
Top 4.8% dependent repos on proxy.golang.org
Top 7.7% forks on proxy.golang.org

proxy.golang.org : github.com/nttcom/eclcloud

Package eclcloud provides interface to Enterprise Cloud. The library has a three-level hierarchy: providers, services, and resources. Provider structs represent the cloud providers that offer and manage a collection of services. You will generally want to create one Provider client per Enterprise Cloud. Use your Enterprise Cloud credentials to create a Provider client. The IdentityEndpoint is typically referred to as "auth_url" or "OS_AUTH_URL" in information provided by the cloud operator. Additionally, the cloud may refer to TenantID or TenantName as project_id and project_name. Credentials are specified like so: You may also use the ecl.AuthOptionsFromEnv() helper function. This function reads in standard environment variables frequently found in an Enterprise Cloud `openrc` file. Again note that Gophercloud currently uses "tenant" instead of "project". Service structs are specific to a provider and handle all of the logic and operations for a particular Enterprise Cloud service. Examples of services include: Compute, Object Storage, Block Storage. In order to define one, you need to pass in the parent provider, like so: Resource structs are the domain models that services make use of in order to work with and represent the state of API resources: Intermediate Result structs are returned for API operations, which allow generic access to the HTTP headers, response body, and any errors associated with the network transaction. To turn a result into a usable resource struct, you must call the Extract method which is chained to the response, or an Extract function from an applicable extension: All requests that enumerate a collection return a Pager struct that is used to iterate through the results one page at a time. Use the EachPage method on that Pager to handle each successive Page in a closure, then use the appropriate extraction method from that request's package to interpret that Page as a slice of results: If you want to obtain the entire collection of pages without doing any intermediary processing on each page, you can use the AllPages method: This top-level package contains utility functions and data types that are used throughout the provider and service packages. Of particular note for end users are the AuthOptions and EndpointOpts structs.

Registry - Source - Documentation - JSON
purl: pkg:golang/github.com/nttcom/eclcloud
License: Apache-2.0
Latest release: over 4 years ago
First release: about 6 years ago
Namespace: github.com/nttcom
Dependent packages: 2
Dependent repositories: 1
Stars: 5 on GitHub
Forks: 6 on GitHub
See more repository details: repos.ecosyste.ms
Last synced: 15 days ago