byteconf-knowledge

Create a client with byteconf.NewClient or NewClientByKeys, passing a callback via WithClientKeyCallback. The SDK maintains a gRPC long connection and invokes your callback whenever the config changes, with updates taking effect in seconds.

Use byteconf.GetConfByOnce for a single key's raw bytes, GetConfModelByOnce for a deserialized model, or GetPathByOnce for all configs under a directory. These suit FaaS scenarios that only need config at startup.

NewClient watches a single config key, NewClientByKeys watches multiple keys, and NewClientByPath recursively watches all configs under a directory with prefix matching. Duplicate listening on the same key is not allowed.

Creating a new client inside a callback causes a deadlock because the SDK's internal listener lock is held during callback execution. Initialize all clients at program startup instead, and panic if NewClient returns an error.

Yes, but you must set the environment variable RUNTIME_IDC_NAME=boe on a Mac so the SDK connects to the BOE environment. Without it, config retrieval will fail in local development.

Cast the returned error to byteconf.NewClientError and call IsNotExist to detect a missing config key. Other error types indicate different failures, which should typically cause the program to panic at startup.