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
  1. Concepts
  2. Campaigns
  3. Campaign Agent

Running Campaigns with GitHub Actions and a Repo-Hosted State File

PreviousSpaceliftNextRunning Campaigns Locally

Last updated 3 months ago

This lets you run a state evaluation without needing CLI access.

Prerequisite

  • An active account on

  • An active list of guardrails in order to generate violations

  • A valid RESOURCELY_API_TOKEN which can be obtained Generate API Token

  • A copy of state file in JSON format - You can find example state file in our scaffolding repo - link

  • A cloned copy of .

To upload evaluation findings for a test state file, you can use the ā€œManually Triggered State Evaluationā€ Github action. This will block evaluations for any config root that has a campaign_config in the Resourcely yaml, so as to avoid polluting any active campaigns that target that config root.

To run an evaluation, then you will need to provide the fields that identify the state file and its associated parameters. Note that you can select a branch other than main, so there’s no need to merge state files into your repo.

A successful evaluation will write the generated findings into the backend. From there, you can interact with campaigns in all the normal ways in the UI. Subsequent state evaluations done through this specific method will update the metrics accordingly if there is a campaign that targets this repository.

Note: To avoid unexpected metrics, it’s best practices to delete any campaigns that are created against this kind of evaluation; metrics added from this cannot be selectively removed if you choose to fully set up campaign proxy evaluations for the config root in question.

https://portal.resourcely.io/
https://github.com/Resourcely-Inc/scaffolding-github-actions-campaigns