메뉴
"Helps developers configure Beckn-ONIX adapter YAML files — covering modules (BAP/BPP), handler steps, plugin wiring (registry, key manager, cache, schema validator, signer, router, publisher, middleware), routing rules, deployment scenarios, and observability setup."
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | beckn-onix-config |
| description | "Helps developers configure Beckn-ONIX adapter YAML files — covering modules (BAP/BPP), handler steps, plugin wiring (registry, key manager, cache, schema validator, signer, router, publisher, middleware), routing rules, deployment scenarios, and observability setup." |
| metadata | {"tags":"beckn,onix,configuration,yaml,bap,bpp,plugins,routing,deployment"} |
All configuration options, parameters, defaults, and examples live in the beckn-onix repo: → GitHub: https://github.com/beckn/beckn-onix/blob/main/CONFIG.md
Always read that document first. It is the single source of truth for every config key.
Use it to answer questions about any of these areas:
| Area | What it documents |
|---|---|
appName, http, log | Top-level app identity, server port/timeouts, log level and destinations |
pluginManager | Local (root) and remote (remoteRoot) plugin binary paths |
modules[] | The four module types: bapTxnReceiver, bapTxnCaller, bppTxnReceiver, bppTxnCaller |
handler | type, role, subscriberId, httpClientConfig, steps[] |
| Plugins | registry, dediregistry, keyManager (vault / secrets / simple), cache (Redis), schemaValidator (v1/v2), signValidator, router, signer, publisher, middleware (reqpreprocessor, reqmapper) |
| Routing rules | routingRules[] — url, bpp, bap, msgq target types; v1 domain-required vs v2 domain-agnostic behaviour; conflict detection |
plugins.otelsetup | OpenTelemetry OTLP export, audit logs, metrics collected per module |
| Deployment scenarios | local-simple, local-vault, production combined, BAP-only, BPP-only |
| Config file layout | Directory structure for config/onix/, config/onix-bap/, config/onix-bpp/ |
path values are correct.domain; v2 rules are domain-agnostic (one rule per endpoint per version).simplekeymanager in a production configdomain on a v2 routing rule when there is already another rule for the same version+endpointsubscriberId on BPP handler if per-module node metrics are neededschemav2validator without setting type (url or file)Understands Beckn 2.0.0 LTS core schema and generates complete, valid sample payloads for all API actions given a use case description. Detects when domain-specific custom schemas are needed and maps them correctly. Covers retail, food & beverage, grocery, EV charging, energy (P2P trading, demand flex), and data marketplace (DDM) domains.
"Guides developers through designing and publishing Beckn 2.0 schemas — from deciding whether a new schema is needed, through authoring, to registry contribution. Covers the four core mental models: check-before-create, abstraction level, inheritance vs composition, and AI-first authoring."
Understands Beckn 2.0.0 LTS core schema and generates complete, valid sample payloads for all API actions given a use case description. Detects when domain-specific custom schemas are needed and maps them correctly. Covers retail, food & beverage, grocery, EV charging, energy (P2P trading, demand flex), and data marketplace (DDM) domains.
Guides developers through designing and publishing Beckn 2.0 schemas — from deciding whether a new schema is needed, through authoring, to registry contribution. Covers the four core mental models: check-before-create, abstraction level, inheritance vs composition, and AI-first authoring.
Helps developers configure Beckn-ONIX adapter YAML files — covering modules (BAP/BPP), handler steps, plugin wiring (registry, key manager, cache, schema validator, signer, router, publisher, middleware), routing rules, deployment scenarios, and observability setup.