When a proposed blueprint is approved, it moves to APPROVED state. A new
revision is committed. The latest committed revision can be used to
create a deployment on Orchestration or Workload Cluster. Edits to an
APPROVED blueprint changes its state back to DRAFT. The last committed
revision of a blueprint represents its latest APPROVED state.
Draft
A blueprint starts in DRAFT state once it is created. All edits are made
to the blueprint in DRAFT state.
Proposed
When the edits are ready for review, blueprint can be proposed and moves
to PROPOSED state. Edits cannot be made to a blueprint in PROPOSED state.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["This documentation covers the `Blueprint.Types.ApprovalState` enum within the Google Cloud Telco Automation v1 API, detailing the different stages of a blueprint's approval lifecycle."],["The `ApprovalState` enum has four possible states: `Approved`, `Draft`, `Proposed`, and `Unspecified`, each representing a specific phase in the blueprint's development and approval process."],["A blueprint begins in the `Draft` state, progresses to `Proposed` for review, and upon approval, transitions to `Approved`, where the latest revision can be deployed."],["The `Approved` state signifies that a new revision of the blueprint has been committed and can be used for deployment, while any edits made will revert its status back to `Draft`."],["The `Unspecified` state is a catch-all for when the state of the Blueprint is not indicated."]]],[]]
