Editing Infrastructure
Edit cloud infrastructure created through Resourcely
Last updated
Edit cloud infrastructure created through Resourcely
Last updated
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.
Coming soon: In addition to the list of pull requests, Resourcely will display a list of blueprint instantiations. This list will be more concise than the list of pull requests.
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.
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.
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.
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.
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.
