23a187d85d
Merge pull request #21739 from hasheddan/s3-backend-comment-typo
...
s3 backend: minor typo in putMD5 comment
2019-07-12 14:01:26 -04:00
cd7bfba141
rebased to terraform master branch
2019-07-10 18:05:10 +01:00
5b9f2fafc8
Standardise directory name for test data
2019-06-30 10:16:15 +02:00
3bc14620c0
backend/remote-state: remove dead code
...
This remote-state adapter is no longer used, because the old remote state
mechanism was removed in Terraform v0.12.
2019-06-18 14:18:05 -07:00
961d43142c
s3 backend: minor typo in putMD5 comment
...
Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
2019-06-15 08:20:37 -05:00
e44ca40702
update remote apply language to use proper its/it's
2019-06-14 12:22:21 -05:00
cb593c25aa
Merge pull request #21381 from davidcelis/remove-cost-estimation
...
Remove pre-alpha cost estimation logic from remote backend
2019-06-13 10:59:56 -04:00
d06609dd23
Swift backend: add application credential support
2019-06-12 17:23:13 +02:00
d8343aa95f
backend/swift: Authentication updates
...
Support for cross-domain authentication has been added and mapping
environment variables to the correct domain settings has been
fixed.
In addition, support for clouds.yaml files has been added.
2019-06-12 08:05:54 -07:00
0c91d227fa
Merge branch 'master' into master
2019-06-10 15:50:59 -04:00
5b6b1663ef
backend/http: implement retries for the http backend ( #19702 )
...
Fixes #19619
2019-06-05 16:12:07 -04:00
b1213f7f6c
backend/local: don't panic when an instance has only a deposed object
...
This unusual situation isn't supposed to arise in normal use, but it can
come up in practice in some edge-case scenarios where Terraform fails in
a severe way during a create_before_destroy.
Some earlier versions of Terraform also had bugs in their handling of
deposed objects, so this may also arise if upgrading from one of those
older versions with some leftover deposed objects in the state.
2019-06-04 09:23:29 -07:00
b6de825723
backend/gcs: make Unlock error message more clear
2019-05-27 20:07:14 -07:00
5ccccfb91f
Remove pre-alpha cost estimation logic
2019-05-20 16:48:38 -07:00
8a6d1d62b6
stringer: Regenerate files with latest version
2019-05-13 15:34:27 +01:00
fc5b186e8d
Don't leak so many connections in the pg backend
...
This change fixes an error I get:
Error: pq: too many connections for role "asdf"
because I can only have so many connections.
2019-04-30 23:34:51 -05:00
394f20f59c
backend/remote: do not unlock after a failed upload
...
When changes are made and we failed to upload the state, we should not
try to unlock the workspace. Leaving the workspace locked is a good
indication something went wrong and also prevents other changes from
being applied before the newest state is properly uploaded.
Additionally we now output the lock ID when a lock or force-unlock
action failed.
2019-04-29 21:23:33 +02:00
151c91ffda
use scanner for reading logs
...
Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>
2019-04-25 11:17:08 -07:00
0e27a8862f
remove duplicate remote output line
...
Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>
2019-04-25 10:52:19 -07:00
bb12206bca
Fixup the tests
2019-04-25 10:32:00 +02:00
7cf744241a
Do not use a scanner to read the logs
...
Using a scanner can cause issues when reading long lines. Also make sure we return the error correctly while planning.
2019-04-25 09:51:52 +02:00
c7a023a95c
update test for new go-tfe version
...
Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>
2019-04-24 16:46:17 -07:00
53f977bee2
TFCE api correct pluralization
...
Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>
2019-04-24 16:44:00 -07:00
e479bd5dc3
update to latest go-tfe
...
same version number but pointing to a new sha
Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>
2019-04-24 16:44:00 -07:00
90bc237b7b
Prevent a panic caused by writing to a nil map
2019-04-11 14:34:14 +02:00
3f44dd9dec
Add tablestore config to store state lock
2019-04-11 07:11:10 +08:00
b887d44712
Add Alibaba Cloud backend OSS with lock
2019-04-11 07:06:43 +08:00
39a95e4222
backend/remote: correctly load remote variables
...
When using `terraform console` in combination with the remote backend, variables defined in Terraform Enterprise were load loaded correctly.
2019-03-28 17:23:48 +01:00
57f6e01830
backend/local: preserve serial and lineage on failure
...
When failing to write the state, the local backend writes the state to a local file called `errrored.tfstate`. Previously it would do so by creating a new state file which would use a new serial and lineage. By exorting the existing state file and directly assigning the new state, the serial and lineage are preserved.
2019-03-27 16:15:16 +01:00
1e32ae243c
grammatical updates to comments and docs ( #20195 )
2019-03-21 14:05:41 -07:00
3ca1253796
backend/gcs: Mark the unused attributes project and region as removed.
...
These two attributes are not used since aec45e6967
2019-03-19 17:29:04 -07:00
9f6a126293
backend/remote: check for external updates
2019-03-08 19:18:07 +01:00
4628fbcc65
Merge pull request #20615 from hashicorp/svh/f-input-context
...
core: add a context to the UIInput interface
2019-03-08 18:44:28 +01:00
e75e845804
Merge pull request #20588 from hashicorp/svh/f-retry
...
backend/remote: also retry on server errors
2019-03-08 18:17:29 +01:00
973e2a7cf9
core: add a context to the UIInput interface
2019-03-08 10:24:40 +01:00
0232d84a0d
backend/remote: also retry on server errors
...
Enably retrying on server errors in the updated `go-tfe` client and add a retry log hook for writing retry messages to the CLI.
2019-03-06 13:36:06 +01:00
b9d8e96e0c
command/plan: plan output should indicate if a resource is being ( #20580 )
...
replaced because the instance was tainted.
2019-03-05 16:18:55 -08:00
709487b4f1
backend: Cap number of "undeclared variable" warnings at four
...
For users who in previous versions have relied on our lack of checking for
whether variables are declared, they may previously have seen an
overwhelming number of warnings when running Terraform v0.12.
Here we cap that number at three specific warnings and then one general
warning, so we can still give a specific source location for the first
couple (for users who have genuinely made a typo) but summarize away a
large number for those who are seeing this because they've not yet
migrated to using environment variables.
2019-03-05 15:42:08 -08:00
34fa67c6b0
Correct pg backend error info
2019-03-05 11:37:08 -08:00
ccf549a62d
Stricter pg backend locking during workspace creation
2019-03-05 11:19:56 -08:00
31c9776d55
Switch pg backend to session-level advisory locking, to avoid rollback of partial state updates
2019-03-04 17:01:08 -08:00
e34a97abca
backend/s3: Add debug logging and user agent
...
Porting over previous behavior from terraform-provider-aws.
2019-02-27 12:59:08 -05:00
63e2dcef8a
Merge pull request #20481 from hashicorp/svh/b-exit-code
...
backend/remote: exit with 1 when a run is canceled
2019-02-27 07:52:20 +01:00
eada955721
Merge pull request #19070 from mars/postgres-backend
...
Postgres backend
2019-02-26 20:20:01 -05:00
6d9e2048f4
Skip more pg backend acceptance tests
2019-02-26 16:50:36 -08:00
920e7a7acc
Mutex pg backend‘s database transaction
2019-02-26 13:45:16 -08:00
c6bf3442fc
Lock() in pg backend now returns LockError for retryable errors
2019-02-26 13:20:40 -08:00
a075a68c58
Correct name of pg backend‘s default schema
2019-02-26 12:59:31 -08:00
01f17fa0ca
backend/remote: exit with 1 when a run is canceled
2019-02-26 21:00:07 +01:00
dd16455a79
fix s3 default region to match provider
2019-02-25 20:27:21 -05:00
Pam Selle