b69c0b4199
oss backend support profile
2019-08-23 21:04:34 +08:00
10d94fb764
Merge pull request #21967 from williams-brian/SSE-C_Remote_State
...
Add support for SSE-C to S3 backend
2019-08-22 17:30:28 -04:00
f3357aad45
vendor: Downgrade Azure dependencies
...
This is to allow Terraform providers to upgrade to at least
one more minor version of the plugin SDK without major UX hiccups.
This concludes (unsuccessful) experiments involving upgrades
to SDK with https://github.com/Azure/go-autorest/pull/455
Even with that patch all providers still experience broken UX
as described in https://github.com/hashicorp/terraform/pull/22490
This downgrade reduces the uncomfort to only a handful of providers
from >100s. The affected providers more or less directly depend on
Azure SDK(s), which is ~8.
Affected providers practically cannot consume Terraform Plugin SDK
with this patch (downgraded Azure SDKs) and can just wait for
extracted Terraform Plugin SDK which is planned to be released soon.
This reverts the following PRs:
- https://github.com/hashicorp/terraform/pull/22247
- https://github.com/hashicorp/terraform/pull/22248
- https://github.com/hashicorp/terraform/pull/22524
- https://github.com/hashicorp/terraform/pull/22525
and it is otherwise result of the following commands
```
go get github.com/Azure/azure-sdk-for-go@v21.3.0
go get github.com/hashicorp/go-azure-helpers@166dfd221bb2
go mod tidy
```
2019-08-20 15:52:11 +01:00
dee450cf8c
vendor: Bump go-azure-helpers to 0.7.0
2019-08-20 09:32:02 +01:00
b459a92575
backend/gcs: Use new endpoints for Google OAuth
...
This is a consequence of googleapis/google-cloud-common#260 .
2019-08-13 15:24:34 -07:00
9631e4c73d
Merge pull request #20571 from sergkondr/fix_misspelling
...
fix misspelling
2019-08-13 17:13:13 -04:00
4bf43efcfd
move hcl2shim package to configs
2019-08-06 19:58:58 -04:00
d43fc71135
modules: update go-azure-helpers to v0.5.0
...
To help address the issues posed on #22087 and #22085 .
2019-08-01 11:57:34 -07:00
a490dfa495
backend/oss: Support for assume role config
2019-07-30 23:27:17 +08:00
412d459292
backend/remote: remove milseading contents from error message ( #22148 )
...
Previously, terraform was returning a potentially-misleading error
message in response to anything other than a 404 from the
b.client.Workspaces.Read operation. This PR simplifies Terraform's error
message with the intent of encouraging those who encounter it to focus
on the error message returned from the tfe client.
The added test is odd, and a bit hacky, and possibly overkill.
2019-07-22 09:06:39 -04:00
190ef537ec
backend/remote: notify users when uploading something other than cwd
...
When a TFC workspace is configured without a VCS root, and with a
working directory, and a user is running `terraform init` from that same
directory, TFC uploads the entire configuration directory, not only the
user's cwd. This is not obvious to the user, so we are adding a descriptive
message explaining what is being uploaded, and why.
2019-07-18 09:50:17 -07:00
89eeaed0a0
[WIP] backend/enhanced: start with absolute configuration path ( #22096 )
...
* backend/enhanced: start with absolute config path
We recently started normalizing the config path before all "command"
operations, which was necessary for consistency but had unexpected
consequences for remote backend operations, specifically when a vcs root
with a working directory are configured.
This PR de-normalizes the path back to an absolute path.
* Check the error and add a test
It turned out all required logic was already present, so I just needed to add a test for this specific use case.
2019-07-17 08:39:37 -04:00
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
5e3c3bafb8
Add support for SSE-C to S3 backend
...
These changes add support for encrypting terraform remote-state in S3 using customer-supplied encryption keys (SSE-C).
2019-07-06 10:10:54 -05: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
yuanye