Glossary

This glossary is meant to serve as a guide to help Resourcely users understand key concepts related to Resourcely.

Resourcely offers the following features to help secure your cloud infrastructure:

• Guardrails: Terraform policy-as-code that determines how cloud resources can be created and altered.

• Campaigns: Remediate existing infrastructure that fails to meet your standards

• Blueprints: Configurable templates used to provision cloud infrastructure resources.

• Foundry: Create custom resources (Blueprints, Guardrails, etc.) by cloning and configuring existing resources or starting from scratch.

• Resources: Manage requests to commit a change from one Git branch to another.

• Global Context: Context-prompting questionnaires used to gather data from developers before provisioning a resource.

• Global Values: Allow admins to define custom drop-downs for customizing terraform infrastructure resource properties before they are provisioned.

• Resourcely.yaml: Separate directory (with separate Terraform variables) within your repository used to define a deployment environment.

• Metrics: Measure the status and health of your environment.

• User management: Import, add and remove users, assign roles and collect contact information.

• Resourcely-cli: a command line utility that helps Resourcely evaluate Guardrails against Terraform plans.

• VCS Proxy: provides secure access to self hosted Version Control System (VCS) APIs, such as GitHub and GitLab, within private networks.

Here are a few additional key concepts:

• Config Roots: A directory containing one or more Terraform files.

• Environments: When creating a pull request in a Config Root that has Environments, users can click the ENV button to supply environment-specific values for most form fields.