Skip to content

conformance.md

Latest commit

 

History

History
48 lines (39 loc) · 1.57 KB

conformance.md

File metadata and controls

48 lines (39 loc) · 1.57 KB
Raw

Conformance

Run validation and conformance before publishing a module. From a fresh public clone:

gh repo clone opencloudtech/CloudRING
cd CloudRING
go mod download
go test ./... -count=1
packages=(./examples/synthetic-service-module/connector-package.json ./reference/synthetic-service/module-package.json ./modules/*/module-package.json)
go run ./cmd/ocsctl validate "${packages[@]}"
go run ./cmd/ocsctl conformance "${packages[@]}"

For a module under review, run the same commands against that module package:

go run ./cmd/ocsctl validate ./reference/synthetic-service/module-package.json
go run ./cmd/ocsctl conformance ./reference/synthetic-service/module-package.json

Use JSON evidence in CI:

mkdir -p evidence
go run ./cmd/ocsctl conformance ./reference/synthetic-service/module-package.json --evidence ./evidence/reference-conformance.json

Conformance checks:

  • canonical OCSv3 package validation;
  • service connector completeness;
  • billing linkage;
  • lifecycle coverage and idempotency;
  • backup, restore, export, delete, retry, rollback;
  • denied, degraded, blocked, retryable, ready states;
  • portal and microfrontend declarations;
  • IAM and tenant access;
  • support diagnostics;
  • evidence bundles and durability;
  • analytics events;
  • provider-neutral public boundary.

Run source-safety before publishing to prove no local host paths, private provider endpoints, hardcoded tokens, or implementation leaks entered public core. Public contributors should keep generated evidence local unless a synthetic receipt is intentionally reviewed for inclusion.