Skip to content

update readme#446

Open
steiler wants to merge 1 commit into
mainfrom
updatereadme
Open

update readme#446
steiler wants to merge 1 commit into
mainfrom
updatereadme

Conversation

@steiler
Copy link
Copy Markdown
Collaborator

@steiler steiler commented Jun 3, 2026

No description provided.

@steiler steiler requested a review from a team as a code owner June 3, 2026 09:55
@steiler steiler force-pushed the updatereadme branch 2 times, most recently from 05d759d to facecdf Compare June 3, 2026 10:08
@codecov
Copy link
Copy Markdown

codecov Bot commented Jun 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment thread README.md
![sdc logo](https://docs.sdcio.dev/assets/logos/SDC-transparent-withname-100x133.png)

This repository is part of Schema Driven Configuration (SDC)
**data-server** is an intent-driven configuration engine for network automation that accommodates mixed operation: northbound **Intents** at explicit **priorities** merge into an effective tree together with **Running**—device configuration the datastore maintains through **Sync** (subscriptions, polling, or one-shot reads)—so CLI edits, Ansible, and other out-of-band changes share the same YANG-backed view as declarative automation. Schema binding is a hard requirement for interpreting and **validating** that tree; southbound drivers—for example **gNMI** or **NETCONF**—apply and refresh state without tying northbound callers to one protocol. Comparing merged intent expectations to **Running** produces **Deviations**; **revertive** intents re-converge on drift and **non-revertive** intents surface divergence without automatic re-push. **Owner** precedence and **blame** record who wins each leaf; **Transactions** follow confirmed-commit semantics with optional **dry-run**, then confirm or cancel/timeout rollback; where a published specification governs wire behaviour, it is the default interoperability contract unless this repository documents a deliberate exception.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would break lines in every 100 chars. I know it is old fashioned, but helps human readeability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants