feat: allow provider-delegated reefs with no rail
Object-storage reefs omit primary_rail and hosted_rails. Scaleway operates S3; reef-storage only names the boundary. Finish RMASTER-WP-0022.
This commit is contained in:
parent
82b7b7295d
commit
654bbe891b
8 changed files with 67 additions and 32 deletions
13
tools/testdata/family-declarations/good/reef-storage-example/declarations/reef.yaml
vendored
Normal file
13
tools/testdata/family-declarations/good/reef-storage-example/declarations/reef.yaml
vendored
Normal file
|
|
@ -0,0 +1,13 @@
|
|||
kind: substrate-reef
|
||||
reef_id: reef-storage-example
|
||||
repo: reef-storage-example
|
||||
ownership_repo: railiance-platform
|
||||
substrate_kind: object-storage
|
||||
lifecycle_state: planned
|
||||
criticality: high
|
||||
current_members: []
|
||||
source_documents:
|
||||
- repo: railiance-master
|
||||
path: docs/reef-substrate-model.md
|
||||
compatibility_notes:
|
||||
- Provider-delegated S3 fixture. No rail. The provider operates the capability.
|
||||
Loading…
Add table
Add a link
Reference in a new issue