-
Notifications
You must be signed in to change notification settings - Fork 2
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
test amend stuff #2424
Open
kneeyo1
wants to merge
5
commits into
main
Choose a base branch
from
kneeyo1-testing-changed-files
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
test amend stuff #2424
Conversation
This file contains 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
kneeyo1
force-pushed
the
kneeyo1-testing-changed-files
branch
from
April 5, 2024 22:22
cf72678
to
9d30bfa
Compare
kneeyo1
force-pushed
the
kneeyo1-testing-changed-files
branch
from
April 5, 2024 22:24
8d0ded8
to
1836b63
Compare
Terraform PlanTACOS generated a terraform plan for 1 slices:
Changesterraform/env.neohuang/behaviors-unlock_on_close/slice-0-projectPlan: 1 to add, 0 to change, 0 to destroy.Commands: (success, tfplan todo)$ cd terraform/env.neohuang/behaviors-unlock_on_close/slice-0-project
direnv: loading $repo/.envrc
direnv: export +GETSENTRY_SAC_DEPLOY_ENVIRON +REPO_TOP
direnv: loading $repo/tacos-gha/.envrc
direnv: export ~PATH ~PS1_PREFIX ~PYTHONPATH
$ GETSENTRY_SAC_VERB=state-admin
$ sudo-gcp tf-lock-acquire
You are authenticated for the next hour as: [email protected]
tf-lock-acquire: success: .([email protected])
$ sudo-gcp terragrunt run-all init
You are authenticated for the next hour as: [email protected]
Initializing the backend...
Initializing provider plugins...
- Reusing previous version of hashicorp/null from the dependency lock file
- Using previously-installed hashicorp/null v3.2.2
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
$ sudo-gcp terragrunt run-all refresh
You are authenticated for the next hour as: [email protected]
null_resource.project: Refreshing state... [id=9141050845234995087]
$ sudo-gcp terragrunt run-all plan -out $slice/tfplan
You are authenticated for the next hour as: [email protected]
time=2024-04-05T22:27:33Z level=error msg=terraform invocation failed in $slice prefix=[$slice]
time=2024-04-05T22:27:33Z level=error msg=Module $slice has finished with an error: 1 error occurred:
* [$slice] exit status 2
prefix=[$slice]
time=2024-04-05T22:27:33Z level=error msg=1 error occurred:
* [$slice] exit status 2 Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# null_resource.project2 will be created
+ resource "null_resource" "project2" {
+ id = (known after apply)
+ triggers = {
+ "project" = "my-prod"
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
─────────────────────────────────────────────────────────────────────────────
Saved the plan to:
tfplan
To perform exactly these actions, run the following command to apply:
terraform apply "tfplan" |
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.