-
Notifications
You must be signed in to change notification settings - Fork 0
Update r2.tf #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
motatoes
wants to merge
1
commit into
main
Choose a base branch
from
motatoes-patch-3
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update r2.tf #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
❌ Failed perform lock action on project: dev failed to lock project: Project diggerhq/testing-lock-mechanism#dev locked by another PR #2(failed to acquire lock dev). The locking plan must be applied or discarded before future plans can execute |
digger plan |
plan for dev 2025-08-06 20:52:39 (UTC)Locking successfulProject diggerhq/testing-lock-mechanism#dev has been locked by PR #3Plan outputTerraform will perform the following actions:
# null_resource.test_r1 will be destroyed
# (because null_resource.test_r1 is not in configuration)
- resource "null_resource" "test_r1" {
- id = "1784346655297594421" -> null
}
# null_resource.test_r2 will be created
+ resource "null_resource" "test_r2" {
+ id = (known after apply)
}
Plan: 1 to add, 0 to change, 1 to destroy.
───────────────────────────────────────────────────────────────────────────── Terraform plan validation check (dev)Terraform plan validation checks succeeded ✅Plan summary
|
digger apply |
apply for dev 2025-08-06 20:55:54 (UTC)Locking successfulProject diggerhq/testing-lock-mechanism#dev has been locked by PR #3Apply outputTerraform will perform the following actions:
# null_resource.test_r1 will be destroyed
# (because null_resource.test_r1 is not in configuration)
- resource "null_resource" "test_r1" {
- id = "1784346655297594421" -> null
}
# null_resource.test_r2 will be created
+ resource "null_resource" "test_r2" {
+ id = (known after apply)
}
Plan: 1 to add, 0 to change, 1 to destroy.
null_resource.test_r1: Destroying... [id=1784346655297594421]
null_resource.test_r1: Destruction complete after 0s
null_resource.test_r2: Creating...
null_resource.test_r2: Creation complete after 0s [id=1802373871144838219]
Apply complete! Resources: 1 added, 0 changed, 1 destroyed.
|
digger apply |
apply for dev 2025-08-06 23:37:15 (UTC)Apply errorcannot perform Apply since the PR is not currently mergeable |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.