Define Support/Customer Policies around Provision Module
Use Case
Define how we want to approach the impact of the Provision module as it falls outside the scope of currently provided services.
Scope of Work
Impacts any customer that chooses to use the Provision module of the Orchestrator.
Contextual Information
- The last thing to think about is that gitlab-orchestrator will spend other companies money and there's a wider blast radius if things don't quite go to plan. If we don't get things right (accidentally spin up 50 instances) or get things really wrong (accidentally delete customer infrastructure not related to Gitlab) we're opening our self up to things we haven't had to think about before.
Acceptance Criteria
The proper parties are comfortable and sign off on how we want to approach supporting the Provision module.