Resourcely Documentation
LoginSign Up
  • Get Started
    • 🎱What is Resourcely?
    • 👋Why Resourcely
    • 🏃Quickstart
      • Terraform policies integrated into CI
      • Remediate policy violations in existing infrastructure
      • Templates for generating Terraform
      • Glossary
  • Concepts
    • Foundry
      • Create Blueprints with Foundry
      • Creating Guardrails with Foundry
      • lmport Terraform Modules
    • Guardrails
      • Writing your own Guardrails
      • Editing Guardrails
      • Releasing Guardrails
      • Enabling Inactive Guardrails
      • Guardrails in Action
        • 🐱GitHub Actions
        • 🦊GitLab Pipelines
    • Campaigns
      • Get started with Campaigns
      • Creating Campaigns
      • Remediate Resources
      • Campaign Agent
        • State File Support
          • Amazon Simple Storage Service (S3)
          • Google Cloud Storage (GCS)
          • HCP Terraform
          • Spacelift
        • Running Campaigns with GitHub Actions and a Repo-Hosted State File
        • Running Campaigns Locally
    • Blueprints
      • Authoring Your Own Blueprints
      • Using Built-in Resourcely Blueprints
      • Configuring Global Contexts
      • Deep Linking
    • Resources
      • Provisioning Infrastructure
      • Editing Infrastructure
      • Shopping Cart
      • Config Roots and Environments
    • Other Features and Settings
      • Global Values
      • Global Context
      • Metrics
      • Resourcely-cli
      • Resourcely.yaml
      • VCS Proxy
      • Settings
        • User management
        • Company Information
        • Notification Settings
        • Change Management
          • 🐱Connect to GitHub
          • 🦊Connect to Gitlab
        • Generate API Token
    • ✨Production Setup
      • Single Sign-On (SSO)
        • Auth0
        • AWS Single Sign-On
        • Azure AD
        • Google Workspace
        • JumpCloud
        • Okta
        • Omnissa Workspace ONE (formerly VMware)
        • OneLogin
        • Ping Identity
        • Other SAML / OIDC Providers
      • Source Code Management
        • Page
        • 🐱GitHub
        • 🦊GitLab
        • Atlassian Bitbucket
        • Azure Repos
  • Tutorials and guides
    • Remediation Use Cases
      • Apply tags to resources for automating backups
      • Implement centralized logging
    • Blueprints Use Cases
      • Automate Data Pipeline Creation
      • Encryption for GCP
      • AWS Account Factory
      • Streamline and govern AI
      • IAM Factory
      • Cost optimization for FinOps
      • Guardrails for Terraform Modules
    • Using the Resourcely Terraform Provider
      • Setup Resourcely Provider
      • Blueprints
      • Guardrails
      • Global Context
  • Integrate
    • CI/CD & Terraform Runners
      • Atlantis
      • 🐟AWS CodeBuild
      • Azure Pipelines
      • Buildkite
      • CircleCI
      • CloudBees CI
      • Codefresh
      • Digger
      • Env0
      • 🎏GitHub Actions
        • 🐱Local Plan
          • 🐹AWS with OpenID Connect
        • 🐶Terraform Cloud Integration
      • 🦊GitLab Pipelines
      • Harness
      • 🗻HashiCorp Cloud Platform (formerly Terraform Cloud)
      • Jenkins
      • Octopus Deploy
      • Scalr
      • 🌌Spacelift
      • Terramate
      • 🌎Terrateam
    • Cloud Providers
      • 🌨️Amazon Web Services (AWS)
      • 🤓Google Cloud Platform (GCP)
        • Guardrail Gaunlet at Google Cloud Next 2025
      • 💾Microsoft Azure
      • Alibaba Cloud
      • Huawei Cloud
      • IBM Cloud
      • Oracle Cloud Infrastructure (OCI)
      • Tencent Cloud
      • VMware vSphere
    • Developer Portals
      • Atlassian Compass
      • Backstage
      • Cortex
      • Harness IDP
      • Home grown internal developer portals
      • OpsLevel
      • Port
      • Roadie
    • ITSM
      • Atlassian Jira
      • FreshWorks
      • ServiceNow ITSM
      • ZenDesk
    • CSPM
      • Wiz
    • More Terraform Provider Integrations
      • 🚂ConductorOne Provider
      • Databricks Provider
      • Kubernetes Provider
      • 🐕Datadog Provider
      • ❄️Snowflake Provider
Powered by GitBook
On this page
  • What happens after you click on Evaluate changes?
  • Request Exception
  • Update Context
  1. Concepts
  2. Campaigns

Remediate Resources

PreviousCreating CampaignsNextCampaign Agent

Last updated 1 month ago

Remediators does not make a distinction about which Campaigns are ongoing: for a remediator, their focus is simply fixing the issue. A remediator can see either a list of repos and config roots with findings that are associated with an active campaign, or they can be given a link directly to the remediation page.

There are two actions a remediator can take for findings. The first is to fix the issue; to this end, the editor will show them all of the findings currently present in the config root.

Try tab completions to see suggested or valid values within the Remediation screen!

The other option is to get an approval.

Typically, in Resourcely change management, findings that are already merged into the codebase are inherently considered approved; to indicate to the change management flow to loop in the appropriate approvers for change management, the remediator can request approvals on any of the preexisting findings. If the associated reviewer group then approves the finding, then that approval will be associated with the finding so that it is no longer considered open once the remediation proposal PR is merged.

What happens after you click on Evaluate changes?

Clicking Evaluate Changes → Evaluate generates a Pull/Merge Request (PR) containing your proposed changes.

The PR will run automated checks that use resourcely-cli to validate your proposed changes. If your changes fix guardrail violations, they will disappear from the Remediate screen once Evaluate finishes.

Until you merge your PR, the findings still exist in Resourcely - you haven’t actually updated your infrastructure yet!

Clicking Submit will add approvers to your PR for any remaining findings or requested exceptions.

When your changes are applied (likely after the PR merges), Resourcely performs a scan of your infrastructure. This scan is what finally resolves the findings in Resourcely.

Request Exception

When you click on Request Exception without making any ****code changes. This is expected, and still involves the creation of a PR. Resourcely will add approvers to the PR and attach information describing your exception requests. You can add description to explain why you are requesting the exception.

After clicking 'Submit,' proceed to 'Evaluate Changes' and then select 'Evaluate.' This action will generate a pull request that includes a detailed description explaining the reason for your exception request.

After that click on 'Evaluate Changes' and then select 'Submit.' This action will finalize the details and request approval from the guardrail default approver.

Update Context

Guardrails can reference context answers. Please refer to and for more details.

When a finding corresponds to a that reference global context question. You can update the context answers and we will store answers in . If you move the answers to a different file, Resourcely will leave them where you put them.

Context
resource-level answer
guardrail
resourcely.tf
Pull Request example of requesting exception