Package alexaforbusiness provides the client and types for making API requests to Alexa For Business. Alexa for Business makes it easy for you to use Alexa in your organization. Alexa for Business gives you the tools you need for managing Alexa devices, enroll your users, and assign skills, at scale. You can build your own context-aware voice skills using the Alexa Skills Kit and the Alexa for Business API operations. You can make also these available as private skills for your organization. Alexa for Business makes it easy to voice-enable your products and services, providing context-aware voice experiences for your customers. See https://docs.aws.amazon.com/goto/WebAPI/alexaforbusiness-2017-11-09 for more information on this service. See alexaforbusiness package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/alexaforbusiness/ To Alexa For Business with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the Alexa For Business client AlexaForBusiness for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/alexaforbusiness/#New
Package abc provides a set of APIs for external use, including APIs for ABC system initialization. It also encompasses functionalities such as traffic distribution for A/B experiments, user configuration data retrieval, user feature flag management, exposure data reporting, and logger registration. Package abc provides a set of APIs for external use, including APIs for ABC system initialization. It also encompasses functionalities such as traffic distribution for A/B experiments, user configuration data retrieval, user feature flag management, exposure data reporting, and logger registration. Package abc is a generated GoMock package. Package abc provides a set of APIs for external use, including APIs for ABC system initialization. It also encompasses functionalities such as traffic distribution for A/B experiments, user configuration data retrieval, user feature flag management, exposure data reporting, and logger registration. Package abc provides a set of APIs for external use, including APIs for ABC system initialization. It also encompasses functionalities such as traffic distribution for A/B experiments, user configuration data retrieval, user feature flag management, exposure data reporting, and logger registration. Package abc provides a set of APIs for external use, including APIs for ABC system initialization. It also encompasses functionalities such as traffic distribution for A/B experiments, user configuration data retrieval, user feature flag management, exposure data reporting, and logger registration. Package abc provides a set of APIs for external use, including APIs for ABC system initialization. It also encompasses functionalities such as traffic distribution for A/B experiments, user configuration data retrieval, user feature flag management, exposure data reporting, and logger registration. Package abc provides a set of APIs for external use, including APIs for ABC system initialization. It also encompasses functionalities such as traffic distribution for A/B experiments, user configuration data retrieval, user feature flag management, exposure data reporting, and logger registration. Package abc provides a set of APIs for external use, including APIs for ABC system initialization. It also encompasses functionalities such as traffic distribution for A/B experiments, user configuration data retrieval, user feature flag management, exposure data reporting, and logger registration. Package abc TODO
Package finspace provides the API client, operations, and parameter types for FinSpace User Environment Management service.
Package workspacesthinclient provides the API client, operations, and parameter types for Amazon WorkSpaces Thin Client. Amazon WorkSpaces Thin Client is an affordable device built to work with Amazon Web Services End User Computing (EUC) virtual desktops to provide users with a complete cloud desktop solution. WorkSpaces Thin Client is a compact device designed to connect up to two monitors and USB devices like a keyboard, mouse, headset, and webcam. To maximize endpoint security, WorkSpaces Thin Client devices do not allow local data storage or installation of unapproved applications. The WorkSpaces Thin Client device ships preloaded with device management software. You can use these APIs to complete WorkSpaces Thin Client tasks, such as creating environments or viewing devices. For more information about WorkSpaces Thin Client, including the required permissions to use the service, see the Amazon WorkSpaces Thin Client Administrator Guide. For more information about using the Command Line Interface (CLI) to manage your WorkSpaces Thin Client resources, see the WorkSpaces Thin Client section of the CLI Reference.
Package content contains all user-supplied content which the system is to manage.
Creates and manages a connetion environment that allows the user to establish TCP connections (outgoing) and listens/accepts connection requests from remote processes.
Package log provides the OpenTelemetry Logs API. This API is separate from its implementation so the instrumentation built from it is reusable. See go.opentelemetry.io/otel/sdk/log for the official OpenTelemetry implementation of this API. The log package provides the OpenTelemetry Logs API, which serves as a standard interface for generating and managing log records within the OpenTelemetry ecosystem. This package allows users to emit LogRecords, enabling structured, context-rich logging that can be easily integrated with observability tools. It ensures that log data is captured in a way that is consistent with OpenTelemetry's data model. This package can be used to create bridges between existing logging libraries and OpenTelemetry. Log bridges allow integrating the existing logging setups with OpenTelemetry. Log bridges can be found in the registry. This package does not conform to the standard Go versioning policy, all of its interfaces may have methods added to them without a package major version bump. This non-standard API evolution could surprise an uninformed implementation author. They could unknowingly build their implementation in a way that would result in a runtime panic for their users that update to the new API. The API is designed to help inform an instrumentation author about this non-standard API evolution. It requires them to choose a default behavior for unimplemented interface methods. There are three behavior choices they can make: All interfaces in this API embed a corresponding interface from go.opentelemetry.io/otel/log/embedded. If an author wants the default behavior of their implementations to be a compilation failure, signaling to their users they need to update to the latest version of that implementation, they need to embed the corresponding interface from go.opentelemetry.io/otel/log/embedded in their implementation. For example, If an author wants the default behavior of their implementations to a panic, they need to embed the API interface directly. This is not a recommended behavior as it could lead to publishing packages that contain runtime panics when users update other package that use newer versions of go.opentelemetry.io/otel/log. Finally, an author can embed another implementation in theirs. The embedded implementation will be used for methods not defined by the author. For example, an author who wants to default to silently dropping the call can use go.opentelemetry.io/otel/log/noop: It is strongly recommended that authors only embed go.opentelemetry.io/otel/log/noop if they choose this default behavior. That implementation is the only one OpenTelemetry authors can guarantee will fully implement all the API interfaces when a user updates their API.
REST/JSON server for managing users and scores.
Package goprobe ... This package the main package exposed to the external world and all the interfaces accessed will be added in this package Package goprobe ... This package is used to establish TCP connection with IA, it uses the configuration details provide in the config.json file Package goprobe ... This is used to handle the panics in the interfaces exposed so that the user application will not crash because of exceptions in the SDK Package goprobe ... Package goprobe ... Package goprobe ... This acts as a wrapper for every http request, users need to call this wrapper for every incoming request to the server
Package session provides user session management.
Package beku provide library for managing Go packages in user's environment (GOPATH or vendor directory).
Package gophercloud provides a multi-vendor interface to OpenStack-compatible clouds. 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 OpenStack cloud. Use your OpenStack credentials to create a Provider client. The IdentityEndpoint is typically refered 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 can authenticate with a token by doing: You may also use the openstack.AuthOptionsFromEnv() helper function. This function reads in standard environment variables frequently found in an OpenStack `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 OpenStack 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. An example retry backoff function, which respects the 429 HTTP response code and a "Retry-After" header: