docs: add repository bootstrap templates
This commit is contained in:
@@ -0,0 +1,13 @@
|
||||
name: Cloud Release
|
||||
|
||||
on:
|
||||
workflow_dispatch:
|
||||
|
||||
jobs:
|
||||
release:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: TODO
|
||||
run: |
|
||||
echo "Add private cloud release pipeline after crank-cloud repository is created."
|
||||
exit 1
|
||||
@@ -0,0 +1,24 @@
|
||||
# crank-cloud
|
||||
|
||||
Private hosted/control-plane repository for Crank.
|
||||
|
||||
## Scope
|
||||
|
||||
This repository is expected to contain:
|
||||
|
||||
- cloud control-plane code
|
||||
- hosted orchestration
|
||||
- metering and billing integrations
|
||||
- hosted tenant management
|
||||
- cloud operational tooling
|
||||
- private cloud deployment and rollout workflows
|
||||
|
||||
It must remain separate from the public Community delivery path and from self-hosted Enterprise packaging.
|
||||
|
||||
## Initial bootstrap checklist
|
||||
|
||||
1. Create the repository as private.
|
||||
2. Copy bootstrap files from this template.
|
||||
3. Define hosted environment owners, release policy and secret model.
|
||||
4. Add cloud-only workflows and manifests.
|
||||
5. Move cloud-owned code only after Community and Enterprise boundaries are already fixed.
|
||||
Reference in New Issue
Block a user