nebius.base.resolver

module documentation
(source)

Service address resolvers used by the SDK and generated clients.

Resolvers map a logical service ID to a network address or address template. For example, a logical ID can be a fully qualified Protocol Buffers service name.

Common usage patterns:

  • Single maps a single explicit id to an address.
  • Prefix maps any service id beginning with a prefix to an address.
  • Basic selects Single or Prefix according to a final * in the ID.
  • Constant always returns the same address regardless of id.
  • Conventional maps names such as nebius.<service>...Service. By default, it returns <service>.{domain}. The api_service_name Protocol Buffers extension can replace the service name.
  • Chain composes multiple resolvers and returns the first match.
  • Cached memoizes results from another resolver.
  • TemplateExpander applies simple string substitutions on resolved
    addresses (useful for replacing templated placeholders such as {domain}).

All resolvers implement Resolver and raise UnknownServiceError when a service id cannot be resolved.

Class Basic Select a Single or Prefix resolver.
Class Cached Memoizing resolver that caches results from another resolver.
Class Chain Compose several resolvers and return the first successful result.
Class Constant Resolver that always returns a fixed address.
Class Conventional Convention-based resolver for Nebius services.
Class Prefix Resolver that matches service ids by prefix.
Class Resolver Abstract resolver interface.
Class Single Resolver that matches a single explicit service id.
Class TemplateExpander Resolver that applies simple string substitutions to results.
Exception UnknownServiceError Raised when a resolver cannot map a service id to an address.
Variable log Undocumented
log = (source) ΒΆ

Undocumented