31 Commits (fa2a76fa239dcd7ebbffecb79ce0ed96bced201b)

Author	SHA1	Message	Date
Sander van Harmelen	8875fa660f	Make sure we also output policies while planning	8 years ago
Sander van Harmelen	775f8a9626	Make sure we always set a custom header ... This is for TFE to recognize were the calls come from.	8 years ago
Sander van Harmelen	0a59e54933	Improve the output just a bit	8 years ago
Sander van Harmelen	c08cd597c5	Omit any empty lines containing STX/ETX markers	8 years ago
Sander van Harmelen	fb0af07696	Print status updates while waiting for the run to start	8 years ago
Sander van Harmelen	d78470ad5a	Don’t ask questions when -auto-approve is set ... We previously asked to override a soft-failed policy, even wehn -auto-approve was set. That is now fixed by returning a policy failed error.	8 years ago
Sander van Harmelen	53a8aaaf85	Merge pull request #19022 from hashicorp/f-auto-apply ... backend/remote: properly handle workspaces that auto apply changes	8 years ago
Sander van Harmelen	194863db4e	Properly handle workspaces that auto apply changes ... This commit adds logic to check if a workspace is configured to auto apply changes. And if it does, we make sure we output all steps correctly.	8 years ago
Sander van Harmelen	b1fdbd7db8	Allow enhanced backends to pass custom exit codes ... In some cases this is needed to keep the UX clean and to make sure any remote exit codes are passed through to the local process. The most obvious example for this is when using the "remote" backend. This backend runs Terraform remotely and stream the output back to the local terminal. When an error occurs during the remote execution, all the needed error information will already be in the streamed output. So if we then return an error ourselves, users will get the same errors twice. By allowing the backend to specify the correct exit code, the UX remains the same while preserving the correct exit codes.	8 years ago
Sander van Harmelen	67db9da000	Add checks for all flags we currently don’t support ... For Plan only: -module-depth=n For Plan & Apply -parallelism=m -refresh=false -var “foo=bar” and -var-file=foo	8 years ago
Sander van Harmelen	ffc67a8e90	Prevent running plan or apply without permissions	8 years ago
Sander van Harmelen	53d322ec69	Test lock timeout errors when running a plan	8 years ago
Sander van Harmelen	c12f0355a7	Revert "Merge pull request #18980 from hashicorp/f-policy-output" ... This reverts commit f09c2db8d2, reversing changes made to 8394dc797d.	8 years ago
Sander van Harmelen	a2241e7c43	backend/remote: introduce support for `-no-color` ... This is a bit of a hack to support the `-no-color` flag while we don’t have an option to set run variables. That is also the reason why the orginal method is commented out instead of deleted. This will be reverted when the TFE starts supporting run variables.	8 years ago
Sander van Harmelen	f09c2db8d2	Merge pull request #18980 from hashicorp/f-policy-output ... backend/remote: only show the full policy output when it fails	8 years ago
Sander van Harmelen	3979aec0ae	Ask to cancel a pending remote operation ... Except when a lock-timeout has exceeded or auto-approve is set.	8 years ago
Sander van Harmelen	37f5ab3500	Only show the full policy output when it fails ... If the policy passes, only show that instead of the full check output to prevent cluttering the output. So a passing policy will only show: ----------------------------------------------- Organization policy check: passed -----------------------------------------------	8 years ago
Sander van Harmelen	b28f47055d	backend/remote: extend mocks and add sentinel tests	8 years ago
Sander van Harmelen	2bd1040bbd	backend/remote: extend mocks and add apply tests	8 years ago
Sander van Harmelen	9f9bbcb0e7	backend/remote: lots of improvements ... This commit adds: - support for `-lock-timeout` - custom error message when a 404 is received - canceling a pending run when TF is Ctrl-C’ed - discard a run when the apply is not approved	8 years ago
Sander van Harmelen	621d589189	backend/remote: add support for the apply operation	8 years ago
Sander van Harmelen	4aeb67b8ff	backend/remote: handle empty results correctly ... The pagination info of a list call that returns an empty list contains: ```go CurrentPage: 1 TotalPages: 0 ``` So checking if we have seen all pages using `CurrentPage == TotalPages` will not work and will result in an endless loop. The tests are updated so they will fail (timeout after 1m) if this is handled incorreclty.	8 years ago
Sander van Harmelen	ea88daa499	backend/remote: add support for state locking	8 years ago
Sander van Harmelen	7c1da2ffaa	Merge pull request #18818 from hashicorp/b-associate-state ... backend/remote: add the run ID to associate state	8 years ago
Sander van Harmelen	cd6d75bc03	backend/remote: add the run ID to associate state ... If a run ID is available, we need to make sure we pass that when creating a new state version so the state will be properly associated with the run.	8 years ago
Sander van Harmelen	3cc58813f0	backend/remote: use a search query and use pagination ... To prevent making unnecessary heavy calls to the backend, we should use a search query to limit the result. But even if we use a search query, we should still use the pagination details to make sure we retrieved all items.	8 years ago
Sander van Harmelen	62ab84a319	backend/remote: compat changes for latest `go-tfe`	8 years ago
Sander van Harmelen	3cfc83e335	backend/remote: take working directories into account ... In TFE you can configure a workspace to use a custom working directory. When determining which directory that needs to be uploaded to TFE, this working directory should be taken into account to make sure we are uploading the correct root directory for the workspace.	8 years ago
Sander van Harmelen	7049d973a9	Do not use the TFE_TOKEN env variable ... Instead promote the use of shared credentials using the CLI Config File	8 years ago
Sander van Harmelen	83d5f4147b	backend/remote: use schema max/min items options	8 years ago
Sander van Harmelen	7fb2d1b8de	Implement the Enterprise enhanced remote backend	8 years ago