Winter Product Update

An automated IDE experience, optional context, and a new scaffolding repo
AUTHOR
Chris Reuter
PUBLISH DATE
November 14, 2024

Today we are announcing our winter product update: new features focused on helping cloud owners customize Resourcely for their organization.

With these updates, our focus is on reducing the time it takes to go from your existing Terraform patterns to reactive, smart forms developers can use to create infrastructure without manual intervention.

These updates are focused on the workflows of cloud owners: teams that own cloud platforms, infrastructure as code, and the developer experience around Terraform. These latest features help cloud owners quickly go from underwater with unending requests to offloading the manual support to Resourcely.

Generate Blueprint tags

When writing custom Blueprints, a typical workflow is to start by copying Terraform from a provider into the Resourcely Foundry IDE. Previously in Resourcely, you would have needed to replace parameter values with {[ variables }} manually.

With tag generation, users can now generate variables with built-in tags with a single click. Simply select the Terraform parameter in question and click “generate tag”. A frontmatter variable reference, as well as an inline variable reference, are created on behalf of the user. This makes the Blueprint creation process significantly faster.

Automatically create Guardrails

We have also introduced the ability to automatically generate a Guardrail based on a Terraform parameter. Given Guardrails can be embedded in Blueprint forms, authors may want to create a Guardrail at the time they are creating a Blueprint variable. Alternatively, they may want to simplify the creation of Guardrails by one-click creating one and then making edits.

To generate a Guardrail automatically, just select a Terraform parameter and select “generate Guardrail”.

Optional Context in Guardrails

Consider a Guardrail that includes context:

WHEN aws_s3_bucket AND CONTEXT environment = "prod"
  REQUIRE bucket STARTS WITH "prod-"
OVERRIDE WITH APPROVAL @platform

If the environment context is missing, Resourcely will request review from the @platform team as a safety precaution. In some cases the absence of a context question is intentional. For those cases, we have added the OPTIONAL clause. To optionally enforce context, write Guardrails with the following syntax:

WHEN aws_s3_bucket AND OPTIONAL CONTEXT environment = "prod"
   REQUIRE bucket STARTS WITH "prod"

Read more about optional context evaluation in our docs!

New scaffolding repo

To make first-time setup easier, we have created a new scaffolding GitHub repo. Simply sign up for Resourcely, fork this repo, and connect to your GitHub account. This repo gives you a free, local Terraform runner based on GitHub Actions.

Stay tuned for our upcoming product updates focused around Campaigns!

Ready to get started?

Set up a time to talk to our team to get started with Resourcely.

Get in touch

More posts

View all
September 27, 2024

Incident Review: The Arc Browser Vulnerability

How you can prevent Firebase misconfiguration
November 11, 2024

Configuration perspectives: AWS S3

Best practices for configuring S3 using Terraform, while taking into account input from a variety of stakeholders

Talk to a Human

See Resourcely in action and learn how it can help you secure and manage your cloud infrastructure today!