public/atlantis
1
0
Fork 0
mirror of https://git.vectorsigma.ru/public/atlantis.git synced 2026-07-29 12:38:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

bump testing-env image (#1582)

Browse Source 
* bump testing-env image

* use correct image

* fix e2e tests

* fix more e2e tests

* one more try

* 0.14.10 works

* one more try

* flippign exp

* flipping tihngs around

* fixing parallel e2e tests
This commit is contained in:
Sarvar Muminov
2021-05-14 10:00:48 -07:00
committed by GitHub
parent 805e94e7f6
commit dbce1d71e7
50 changed files with 232 additions and 344 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.circleci/config.yml
View File

@@ -2,7 +2,7 @@ version: 2
jobs:
test:
docker:
- image: runatlantis/testing-env:20296f9638a4eca04733f60b39e1d3025b9d708a
- image: runatlantis/testing-env:805e94e7f648eddb0484e539a7b51410d39529bc
steps:
- checkout
- run: make test-all

77
server/events_controller_e2e_test.go
View File

@@ -1037,44 +1037,61 @@ func assertCommentEquals(t *testing.T, expReplies []string, act string, repoDir
resourceRegex := regexp.MustCompile(`null_resource\.simple(\[\d])?\d?:.*`)
act = resourceRegex.ReplaceAllString(act, "null_resource.simple:")
// For parallel plans and applies, do a substring match since output may be out of order
var replyMatchesExpected func(string, string) bool
// For parallel plans and applies, we go through all expected replies and
// look for any 1 match. They can be out of order
if parallel {
replyMatchesExpected = func(act string, expStr string) bool {
return strings.Contains(act, expStr)
}
} else {
replyMatchesExpected = func(act string, expStr string) bool {
return expStr == act
}
}
for _, expFile := range expReplies {
exp, err := ioutil.ReadFile(filepath.Join(absRepoPath(t, repoDir), expFile))
Ok(t, err)
expStr := string(exp)
// My editor adds a newline to all the files, so if the actual comment
// doesn't end with a newline then strip the last newline from the file's
// contents.
if !strings.HasSuffix(act, "\n") {
expStr = strings.TrimSuffix(expStr, "\n")
anyMatch := false
for _, expFile := range expReplies {
exp, err := ioutil.ReadFile(filepath.Join(absRepoPath(t, repoDir), expFile))
Ok(t, err)
expStr := string(exp)
// My editor adds a newline to all the files, so if the actual comment
// doesn't end with a newline then strip the last newline from the file's
// contents.
if !strings.HasSuffix(act, "\n") {
expStr = strings.TrimSuffix(expStr, "\n")
}
anyMatch = expStr == act
}
if !replyMatchesExpected(act, expStr) {
if !anyMatch {
// If in CI, we write the diff to the console. Otherwise we write the diff
// to file so we can use our local diff viewer.
if os.Getenv("CI") == "true" {
t.Logf("exp: %s, got: %s", expStr, act)
t.Logf("got: %s, \nnone of the expected fixtures matches", act)
t.FailNow()
} else {
actFile := filepath.Join(absRepoPath(t, repoDir), expFile+".act")
err := ioutil.WriteFile(actFile, []byte(act), 0600)
Ok(t, err)
cwd, err := os.Getwd()
Ok(t, err)
rel, err := filepath.Rel(cwd, actFile)
Ok(t, err)
t.Errorf("%q was different, wrote actual comment to %q", expFile, rel)
t.Errorf("got: %s, \nnone of the expected fixtures matches", act)
}
}
} else {
for _, expFile := range expReplies {
exp, err := ioutil.ReadFile(filepath.Join(absRepoPath(t, repoDir), expFile))
Ok(t, err)
expStr := string(exp)
// My editor adds a newline to all the files, so if the actual comment
// doesn't end with a newline then strip the last newline from the file's
// contents.
if !strings.HasSuffix(act, "\n") {
expStr = strings.TrimSuffix(expStr, "\n")
}
if expStr != act {
// If in CI, we write the diff to the console. Otherwise we write the diff
// to file so we can use our local diff viewer.
if os.Getenv("CI") == "true" {
t.Logf("exp: %s, got: %s", expStr, act)
t.FailNow()
} else {
actFile := filepath.Join(absRepoPath(t, repoDir), expFile+".act")
err := ioutil.WriteFile(actFile, []byte(act), 0600)
Ok(t, err)
cwd, err := os.Getwd()
Ok(t, err)
rel, err := filepath.Rel(cwd, actFile)
Ok(t, err)
t.Errorf("%q was different, wrote actual comment to %q", expFile, rel)
}
}
}
}

7
server/testfixtures/test-repos/automerge/exp-output-apply-dir1.txt
View File

@@ -6,12 +6,5 @@ null_resource.automerge[0]: Creation complete after *s [id=*******************]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
```

7
server/testfixtures/test-repos/automerge/exp-output-apply-dir2.txt
View File

@@ -6,12 +6,5 @@ null_resource.automerge[0]: Creation complete after *s [id=*******************]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
```

8
server/testfixtures/test-repos/automerge/exp-output-autoplan.txt
View File

@@ -8,8 +8,8 @@ Ran Plan for 2 projects:
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:
@@ -37,8 +37,8 @@ Plan: 1 to add, 0 to change, 0 to destroy.
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

10
server/testfixtures/test-repos/modules-yaml/exp-output-apply-production.txt
View File

@@ -1,24 +1,14 @@
Ran Apply for dir: `production` workspace: `default`
<details><summary>Show Output</summary>
```diff
module.null.null_resource.this: Creating...
module.null.null_resource.this: Creation complete after *s [id=*******************]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "production"
```
</details>

10
server/testfixtures/test-repos/modules-yaml/exp-output-apply-staging.txt
View File

@@ -1,24 +1,14 @@
Ran Apply for dir: `staging` workspace: `default`
<details><summary>Show Output</summary>
```diff
module.null.null_resource.this: Creating...
module.null.null_resource.this: Creation complete after *s [id=*******************]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "staging"
```
</details>

8
server/testfixtures/test-repos/modules-yaml/exp-output-autoplan.txt
View File

@@ -8,8 +8,8 @@ Ran Plan for 2 projects:
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:
@@ -40,8 +40,8 @@ Plan: 1 to add, 0 to change, 0 to destroy.
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

10
server/testfixtures/test-repos/modules/exp-output-apply-production.txt
View File

@@ -1,24 +1,14 @@
Ran Apply for dir: `production` workspace: `default`
<details><summary>Show Output</summary>
```diff
module.null.null_resource.this: Creating...
module.null.null_resource.this: Creation complete after *s [id=*******************]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "production"
```
</details>

10
server/testfixtures/test-repos/modules/exp-output-apply-staging.txt
View File

@@ -1,24 +1,14 @@
Ran Apply for dir: `staging` workspace: `default`
<details><summary>Show Output</summary>
```diff
module.null.null_resource.this: Creating...
module.null.null_resource.this: Creation complete after *s [id=*******************]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "staging"
```
</details>

4
server/testfixtures/test-repos/modules/exp-output-autoplan-only-staging.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `staging` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

4
server/testfixtures/test-repos/modules/exp-output-plan-production.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `production` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

4
server/testfixtures/test-repos/modules/exp-output-plan-staging.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `staging` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

10
server/testfixtures/test-repos/policy-checks-apply-reqs/exp-output-apply.txt
View File

@@ -1,24 +1,14 @@
Ran Apply for dir: `.` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
workspace = "default"
```
</details>

4
server/testfixtures/test-repos/policy-checks-apply-reqs/exp-output-autoplan.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `.` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

4
server/testfixtures/test-repos/policy-checks-diff-owner/exp-output-autoplan.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `.` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

10
server/testfixtures/test-repos/policy-checks-extra-args/exp-output-apply.txt
View File

@@ -1,24 +1,14 @@
Ran Apply for dir: `.` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
workspace = "default"
```
</details>

15
server/testfixtures/test-repos/policy-checks-extra-args/exp-output-auto-policy-check.txt.act
View File

@@ -1,15 +0,0 @@
Ran Policy Check for dir: `.` workspace: `default`
**Policy Check Error**
```
exit status 1
Checking plan against the following policies:
test_policy
FAIL - <redacted plan file> - null_resource_policy - WARNING: Null Resource creation is prohibited.
1 test, 0 passed, 0 warnings, 1 failure, 0 exceptions
```
* :heavy_check_mark: To **approve** failing policies either request an approval from approvers or address the failure by modifying the codebase.

4
server/testfixtures/test-repos/policy-checks-extra-args/exp-output-autoplan.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `.` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

10
server/testfixtures/test-repos/policy-checks-multi-projects/exp-output-apply.txt
View File

@@ -4,27 +4,17 @@ Ran Apply for 2 projects:
1. dir: `dir2` workspace: `default`
### 1. dir: `dir1` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
workspace = "default"
```
</details>
---
### 2. dir: `dir2` workspace: `default`

8
server/testfixtures/test-repos/policy-checks-multi-projects/exp-output-autoplan.txt
View File

@@ -8,8 +8,8 @@ Ran Plan for 2 projects:
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:
@@ -40,8 +40,8 @@ Plan: 1 to add, 0 to change, 0 to destroy.
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

10
server/testfixtures/test-repos/policy-checks/exp-output-apply.txt
View File

@@ -1,24 +1,14 @@
Ran Apply for dir: `.` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
workspace = "default"
```
</details>

4
server/testfixtures/test-repos/policy-checks/exp-output-autoplan.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `.` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

10
server/testfixtures/test-repos/server-side-cfg/exp-output-apply-default-workspace.txt
View File

@@ -1,24 +1,14 @@
Ran Apply for dir: `.` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
workspace = "default"
```
</details>

10
server/testfixtures/test-repos/server-side-cfg/exp-output-apply-staging-workspace.txt
View File

@@ -1,24 +1,14 @@
Ran Apply for dir: `.` workspace: `staging`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
workspace = "staging"
```
</details>

8
server/testfixtures/test-repos/server-side-cfg/exp-output-autoplan.txt
View File

@@ -10,8 +10,8 @@ Ran Plan for 2 projects:
preinit custom
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:
@@ -46,8 +46,8 @@ Plan: 1 to add, 0 to change, 0 to destroy.
preinit staging
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

17
server/testfixtures/test-repos/simple-yaml/exp-output-apply-all.txt
View File

@@ -4,28 +4,18 @@ Ran Apply for 2 projects:
1. dir: `.` workspace: `staging`
### 1. dir: `.` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "fromconfig"
workspace = "default"
```
</details>
---
### 2. dir: `.` workspace: `staging`
@@ -39,13 +29,6 @@ null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "fromfile"

10
server/testfixtures/test-repos/simple-yaml/exp-output-apply-default.txt
View File

@@ -1,25 +1,15 @@
Ran Apply for dir: `.` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "fromconfig"
workspace = "default"
```
</details>

7
server/testfixtures/test-repos/simple-yaml/exp-output-apply-staging.txt
View File

@@ -10,13 +10,6 @@ null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "fromfile"

8
server/testfixtures/test-repos/simple-yaml/exp-output-autoplan.txt
View File

@@ -10,8 +10,8 @@ Ran Plan for 2 projects:
preinit
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:
@@ -45,8 +45,8 @@ Plan: 1 to add, 0 to change, 0 to destroy.
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

14
server/testfixtures/test-repos/simple/exp-output-apply-var-all.txt
View File

@@ -16,13 +16,6 @@ null_resource.simple:
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "default_workspace"
@@ -45,13 +38,6 @@ null_resource.simple:
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "new_workspace"

7
server/testfixtures/test-repos/simple/exp-output-apply-var-default-workspace.txt
View File

@@ -12,13 +12,6 @@ null_resource.simple:
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "default_workspace"

7
server/testfixtures/test-repos/simple/exp-output-apply-var-new-workspace.txt
View File

@@ -12,13 +12,6 @@ null_resource.simple:
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "new_workspace"

7
server/testfixtures/test-repos/simple/exp-output-apply-var.txt
View File

@@ -12,13 +12,6 @@ null_resource.simple:
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "overridden"

7
server/testfixtures/test-repos/simple/exp-output-apply.txt
View File

@@ -12,13 +12,6 @@ null_resource.simple:
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
Outputs:
var = "default"

4
server/testfixtures/test-repos/simple/exp-output-atlantis-plan-new-workspace.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `.` workspace: `new_workspace`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

4
server/testfixtures/test-repos/simple/exp-output-atlantis-plan-var-overridden.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `.` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

4
server/testfixtures/test-repos/simple/exp-output-atlantis-plan.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `.` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

4
server/testfixtures/test-repos/simple/exp-output-autoplan.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for dir: `.` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

10
server/testfixtures/test-repos/tfvars-yaml-no-autoplan/exp-output-apply-default.txt
View File

@@ -1,25 +1,15 @@
Ran Apply for project: `default` dir: `.` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: default.tfstate
Outputs:
var = "default"
workspace = "default"
```
</details>

10
server/testfixtures/test-repos/tfvars-yaml-no-autoplan/exp-output-apply-staging.txt
View File

@@ -1,25 +1,15 @@
Ran Apply for project: `staging` dir: `.` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: staging.tfstate
Outputs:
var = "staging"
workspace = "default"
```
</details>

4
server/testfixtures/test-repos/tfvars-yaml-no-autoplan/exp-output-plan-default.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for project: `default` dir: `.` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

4
server/testfixtures/test-repos/tfvars-yaml-no-autoplan/exp-output-plan-staging.txt
View File

@@ -4,8 +4,8 @@ Ran Plan for project: `staging` dir: `.` workspace: `default`
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

10
server/testfixtures/test-repos/tfvars-yaml/exp-output-apply-default.txt
View File

@@ -1,25 +1,15 @@
Ran Apply for project: `default` dir: `.` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: default.tfstate
Outputs:
var = "default"
workspace = "default"
```
</details>

10
server/testfixtures/test-repos/tfvars-yaml/exp-output-apply-staging.txt
View File

@@ -1,25 +1,15 @@
Ran Apply for project: `staging` dir: `.` workspace: `default`
<details><summary>Show Output</summary>
```diff
null_resource.simple:
null_resource.simple:
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: staging.tfstate
Outputs:
var = "staging"
workspace = "default"
```
</details>

8
server/testfixtures/test-repos/tfvars-yaml/exp-output-autoplan.txt
View File

@@ -8,8 +8,8 @@ Ran Plan for 2 projects:
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:
@@ -43,8 +43,8 @@ Plan: 1 to add, 0 to change, 0 to destroy.
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:

27
server/testfixtures/test-repos/workspace-parallel-yaml/exp-output-apply-all-production.txt
View File

@@ -1,21 +1,34 @@
<details><summary>Show Output</summary>
Ran Apply for 2 projects:
1. dir: `staging` workspace: `staging`
1. dir: `production` workspace: `production`
### 1. dir: `staging` workspace: `staging`
```diff
null_resource.this: Creating...
null_resource.this: Creation complete after *s [id=*******************]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
Outputs:
State path: terraform.tfstate
workspace = "staging"
```
---
### 2. dir: `production` workspace: `production`
```diff
null_resource.this: Creating...
null_resource.this: Creation complete after *s [id=*******************]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
Outputs:
workspace = "production"
```
</details>
---

27
server/testfixtures/test-repos/workspace-parallel-yaml/exp-output-apply-all-staging.txt
View File

@@ -1,21 +1,34 @@
<details><summary>Show Output</summary>
Ran Apply for 2 projects:
1. dir: `production` workspace: `production`
1. dir: `staging` workspace: `staging`
### 1. dir: `production` workspace: `production`
```diff
null_resource.this: Creating...
null_resource.this: Creation complete after *s [id=*******************]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
Outputs:
State path: terraform.tfstate
workspace = "production"
```
---
### 2. dir: `staging` workspace: `staging`
```diff
null_resource.this: Creating...
null_resource.this: Creation complete after *s [id=*******************]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
Outputs:
workspace = "staging"
```
</details>
---

49
server/testfixtures/test-repos/workspace-parallel-yaml/exp-output-autoplan-production.txt
View File

@@ -1,9 +1,15 @@
Ran Plan for 2 projects:
1. dir: `production` workspace: `production`
1. dir: `staging` workspace: `staging`
### 1. dir: `production` workspace: `production`
<details><summary>Show Output</summary>
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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:
@@ -26,3 +32,42 @@ Changes to Outputs:
* :repeat: To **plan** this project again, comment:
* `atlantis plan -d production -w production`
</details>
Plan: 1 to add, 0 to change, 0 to destroy.
---
### 2. dir: `staging` workspace: `staging`
<details><summary>Show Output</summary>
```diff
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.this will be created
+ resource "null_resource" "this" {
+ id = (known after apply)
}
Plan: 1 to add, 0 to change, 0 to destroy.
Changes to Outputs:
+ workspace = "staging"
```
* :arrow_forward: To **apply** this plan, comment:
* `atlantis apply -d staging -w staging`
* :put_litter_in_its_place: To **delete** this plan click [here](lock-url)
* :repeat: To **plan** this project again, comment:
* `atlantis plan -d staging -w staging`
</details>
Plan: 1 to add, 0 to change, 0 to destroy.
---
* :fast_forward: To **apply** all unapplied plans from this pull request, comment:
* `atlantis apply`
* :put_litter_in_its_place: To delete all plans and locks for the PR, comment:
* `atlantis unlock`

49
server/testfixtures/test-repos/workspace-parallel-yaml/exp-output-autoplan-staging.txt
View File

@@ -1,9 +1,47 @@
Ran Plan for 2 projects:
1. dir: `production` workspace: `production`
1. dir: `staging` workspace: `staging`
### 1. dir: `production` workspace: `production`
<details><summary>Show Output</summary>
```diff
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
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.this will be created
+ resource "null_resource" "this" {
+ id = (known after apply)
}
Plan: 1 to add, 0 to change, 0 to destroy.
Changes to Outputs:
+ workspace = "production"
```
* :arrow_forward: To **apply** this plan, comment:
* `atlantis apply -d production -w production`
* :put_litter_in_its_place: To **delete** this plan click [here](lock-url)
* :repeat: To **plan** this project again, comment:
* `atlantis plan -d production -w production`
</details>
Plan: 1 to add, 0 to change, 0 to destroy.
---
### 2. dir: `staging` workspace: `staging`
<details><summary>Show Output</summary>
```diff
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:
@@ -26,3 +64,10 @@ Changes to Outputs:
* :repeat: To **plan** this project again, comment:
* `atlantis plan -d staging -w staging`
</details>
Plan: 1 to add, 0 to change, 0 to destroy.
---
* :fast_forward: To **apply** all unapplied plans from this pull request, comment:
* `atlantis apply`
* :put_litter_in_its_place: To delete all plans and locks for the PR, comment:
* `atlantis unlock`