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 details the `Blueprint.Types.ApprovalState` enum within the Google Cloud Telco Automation v1 API, outlining the different stages a blueprint can be in."],["The `ApprovalState` enum has four states: `Approved`, representing a blueprint ready for deployment; `Draft`, the initial state for edits; `Proposed`, indicating a blueprint ready for review; and `Unspecified` for an undefined state."],["A blueprint starts in the `Draft` state, transitions to `Proposed` for review, and upon approval, moves to `Approved` for deployment, with edits to an `Approved` blueprint reverting it back to `Draft`."],["The documentation is specific to version 1.1.0, which can be referenced in the link provided, but they also include links for versions 1.2.0 and 1.0.0."]]],[]]
