Telco Automation v1 API - Class Blueprint (1.2.0)

Reference documentation and code samples for the Telco Automation v1 API class Blueprint.

A Blueprint contains a collection of kubernetes resources in the form of YAML files. The file contents of a blueprint are collectively known as package. A blueprint can be a) imported from TNA's public catalog b) modified as per a user's need c) proposed and approved. On approval, a revision of blueprint is created which can be used to create a deployment on Orchestration or Workload Cluster.

Output only. Approval state of the blueprint (DRAFT, PROPOSED, APPROVED)

BlueprintName-typed view over the Name resource name property.

Output only. Blueprint creation time.

Output only. DeploymentLevel of a blueprint signifies where the blueprint will be applied. e.g. [HYDRATION, SINGLE_DEPLOYMENT, MULTI_DEPLOYMENT]

Optional. Human readable name of a Blueprint.

Optional. Files present in a blueprint. When invoking UpdateBlueprint API, only the modified files should be included in this. Files that are not included in the update of a blueprint will not be changed.

Optional. Labels are key-value attributes that can be set on a blueprint resource by the user.

The name of the blueprint. If unspecified, the name will be autogenerated from server side. Name of the blueprint must not contain @ character.

Output only. Name of the repository where the blueprint files are stored.

Output only. The timestamp that the revision was created.

Output only. Immutable. The revision ID of the blueprint. A new revision is committed whenever a blueprint is approved.

Output only. Indicates if the deployment created from this blueprint can be rolled back.

Required. Immutable. The public blueprint ID from which this blueprint was created.

Output only. Source provider is the author of a public blueprint, from which this blueprint is created.

Output only. The timestamp when the blueprint was updated.