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
  • How to start editing
  • Editing a pull request
  • Unmerged PR
  • Merged or Closed PR
  • Handling changes
  1. Concepts
  2. Resources

Editing Infrastructure

Edit cloud infrastructure created through Resourcely

PreviousProvisioning InfrastructureNextShopping Cart

Last updated 3 months ago

How to start editing

You can edit infrastructure starting from any Pull Request that has touched that infrastructure. Resourcely tracks existing open, merged, and closed PRs created by its users.

Resourcely keeps track of the resources changed by each PR. When you edit a PR, Resourcely will update (or remove) those resources in your Terraform code. Resourcely ensures that the new changes do not violate any guardrail requirements.

Editing a pull request

In general, when you edit a pull request, you'll see the create form "as it was" when Resourcely last updated the infrastructure created by that pull request.

Editing a pull request behaves slightly differently depending on whether the PR is unmerged, merged, or closed.

Unmerged PR

  • You can only edit PRs that belong to you. Resourcely won't help edit someone else's branch.

  • At the end of the process, Resourcely will add a new commit to your PR's branch.

Merged or Closed PR

  • You can edit merged PRs even if they don’t belong to you.

  • Resourcely first checks for any unmerged PRs that might have changed the same infrastructure. If found, it switches to the 'unmerged PR' process.

  • At the end of the process, Resourcely will create a new PR.

Handling changes

When editing, many things might have changed that influence the "shape" (schema) of the create form:

  • The blueprint

  • The set of global context questions that apply to the blueprint

  • The set of allowed answers for single-select and multi-select global context questions

  • Global values referenced by the blueprint

  • The config root that the PR produced Terraform into

If there are newer version of the PR's blueprints, Resourcely will automatically use the newer versions. For other kinds of changes, Resourcely generally responds by removing data from the form if it no longer fits.

Let's consider a global context question like "What is the tier of this infrastructure?" as an example. If the PR you're editing answered "tier 4" but that is no longer a valid choice, then you will have to answer this question again (using the new set of choices) when editing.

Pull Requests Page with Edit Support
Edit page loader