Manage Infrastructure as Code (IaC)

Learn how to change IaC major, minor version and stream from your Control Plane

Suggest Edits

Facets provides users with the capability to change the major and minor IaC version and stream directly from the Control Plane.

Table of Contents

IaC in Facets

Infrastructure as Code (IaC) is the managing and provisioning of infrastructure through your Control Plane instead of through manual processes.

Facets provides these three different streams of IaC in your Control Plane for consistent, error free deployments:

  • Production
  • Staging
  • Development

Use Cases

By using IaC versions, users can get the following advantages over traditional manual deployments:

  • Fixed version for your IaC
    Maintaining consistency across environments is as simple as deploying with a fixed IaC version and provides the additional benefit of having immutable infrastructure.
  • Staging IaC as a precursor for upcoming changes
    Users can test their environments reliably in the Staging IaC, to ensure zero down-time when they deploy resources in Production IaC.
  • Major version upgrade
    Users can update their environments in a safe manner by testing and deploying resources using a major version of IaC in the staging stream, then migrating the neccessary environments to the next major version.

Prerequisites to manage IaC versions

  • An environment with resources must exist in the blueprint where your infrastructure has been added in the definition.

📘

NOTE

If there is no defined IaC version for an environment during deployment, Facets will automatically select the latest version of IaC from PRODUCTION stream.

Manage IaC Version from your Control Plane

Facets allows you to manage the IaC version from your Environment Overview screen as well as Releases screen.

📘

NOTE

IaC version or stream change will take effect from the next release after the change.

Using Environment Overview screen

  1. Login to your Control Plane.
  2. Select a Blueprint.
Select a Blueprint (Click on the image to expand)

Select a Blueprint (Click on the image to expand)

  1. Select the Environment in your defined Blueprint where you want to manage IaC version.
Select an Environment (Click on the image to expand)

Select an Environment (Click on the image to expand)

  1. In the Environment Overview page, click on EDIT button in the IaC Version widget.
Edit button in IaC Version widget (Click on the image to expand)

Edit button in IaC Version widget (Click on the image to expand)

  1. Fill in the changes in the Edit IaC Version window that appears on screen, and click Save Changes to apply your changes.
Edit IaC Version popup window (Click on the image to expand)

Edit IaC Version popup window (Click on the image to expand)

  1. You should see a success toaster popup confirming your changes.
Success toaster (Click on the image to expand)

Success toaster (Click on the image to expand)

Using Releases screen

📘

Follow Steps 1-3 from the Using Environment Overview screen section.

  1. Navigate to Releases screen using the sidebar navigation.
Click on the Releases button in the Navigation bar (Click on the image to expand)

Click on the Releases button in the Navigation bar (Click on the image to expand)

  1. Click on the Ellipsis button to view more options and select Update IaC Version.
Update IaC Version button in other settings (Click on the image to expand)

Update IaC Version button in other settings (Click on the image to expand)

  1. Fill in the changes in the Edit IaC Version window that appears on screen, and click Save Changes to apply your changes.
Edit IaC Version popup window (Click on the image to expand)

Edit IaC Version popup window (Click on the image to expand)

  1. You should see a success toaster popup confirming your changes.
Success toaster (Click on the image to expand)

Success toaster (Click on the image to expand)

Constraints

  • The IaC version change will take effect from the next release.
  • For the major version, user can only update to a newer upgraded version. It not possible to move to a lower version. For example, if a user is using major version 1, it is not possible to move to 0.

Updated 4 months ago