Baseline validation rules for electrical products
product://community/electrical-baseline- Validated
- Community maintained
Use repository
Everything below is pinned to 1.0. Change the revision in the context bar above.
product pull community/electrical-baseline@1.0 \
--include products,attributesproduct pull community/electrical-baseline@sha256:45b1d8979f298670bfb64a79fd6bb6c2c6774dfc1a780076bada5ef4a54f28a7Commit sha256:45b1d8979f29… full digest sha256:45b1d8979f298670bfb64a79fd6bb6c2c6774dfc1a780076bada5ef4a54f28a7
Approximate download size: 2.6 kB (compressed Parquet).
Use is governed by CC-BY-4.0.
CLI reference · Install: brew install product-cloud/tap/product
curl -s "https://api.product.cloud/v1/repos/community/electrical-baseline/products?revision=1.0"Use is governed by CC-BY-4.0.
| File | Format | Size | Checksum |
|---|---|---|---|
| data/rules-0000.parquet | parquet | 2.6 kB | sha256:eb76ca1e7cb1… full digest sha256:eb76ca1e7cb1925e3dd7826530a4456f19de4a6309ad70246a0fd17a5ec7277f |
Files of release 1.0. Open objects are immutable and cached at objects.product.cloud; restricted objects are delivered through short-lived signed links after an entitlement check.
Use is governed by CC-BY-4.0.
- Follow
- See releases and discussions in your dashboard.
- Subscribe
- Receive signed webhooks for selected events.
- Sync
- Apply changes to a target system, with a dry-run plan first.
product webhook create community/electrical-baseline \
--events release.published,repo.ref.updated \
--url https://hooks.example.com/product-cloudcurl -s "https://api.product.cloud/v1/repos/community/electrical-baseline/changes?after=$CURSOR&limit=1000"product sync plan community/electrical-baseline \
--target ./local-mirror \
--checkpoint .product/checkpoints/electrical-baseline.jsonMirror the pinned release into a Guardian pool, then land it through review.
gdn pool add electrical-baseline --from product://community/electrical-baseline@1.0
gdn pool sync electrical-baseline
gdn pool land electrical-baseline --via-reviewOther certified connectors appear here with equal placement as soon as they pass the public product.cloud conformance suite. Listing order carries no preference.