terraform

Commit Graph

Author	SHA1	Message	Date
Daniel Banck	2b9d25c7fd	Add `terraform query` subcommand (TF-25494) (#37174 ) * WIP * Reuse plan command for query CLI * Basic CLI output * Only fail a list request on error * poc: store query results in separate field * WIP: odd mixture between JSONs * Fix list references * Separate JSON rendering The structured JSON now only logs a status on which list query is currently running. The new jsonlist package can marshal the query fields of a plan. * Remove matcher * Store results in an extra struct * Structured list result logging * Move list result output into hooks * Add help text and additional flag * Disable query runs with the cloud backend for now * Review feedback	10 months ago
Rémi Lapeyre	5a8de9d70d	Add TRACE logs when uploading to the cloud and remote backends (#36757 ) Co-authored-by: Liam Cervante <liam.cervante@hashicorp.com>	1 year ago
latentd	5edcdef6fc	update legacy term: Terraform Cloud agent => HCP Terraform Agent	1 year ago
Sebastian Rivera	fb06df80fc	Refactor generalError to use appName In order to inject the value of TFP-AppName, we will need a backend.Cloud ref available to use. This change modifies generalError as a receiver method for backend.Cloud types. We also duplicate this method as a receiver for TestSuiteRunner, since TestSuiteRunner does not have a backend.Cloud ref.	2 years ago
Sebastian Rivera	015f795ff0	Rebrand Terraform Cloud to HCP Terraform	2 years ago
Martin Atkins	88cb4aeea3	backendrun: Separate the types/etc for backends that support operations We previously had all of the types and helpers for all kinds of backends together in package backend. That kept things relatively simple, but it also meant that the majority of backends that only deal with remote state storage ended up still indirectly depending on the entire Terraform modules runtime, configuration loader, etc, etc, which brings into scope a bunch of external dependencies that the remote state backends don't really need. Since backends that support operations are a rare exception, we'll move the types and helpers for those into a separate package "backendrun", and then the main package backend can have a much more modest set of types and, more importantly, a modest set of dependencies on other packages in this codebase. This is part of an ongoing effort to reduce the exposure of Terraform Core and CLI code to the remote backends and vice-versa, so that in the long run we can more often treat them as separate for dependency maintenance purposes.	2 years ago
Lauren	6d9b3b2cd7	call Colorize() on CLI output	2 years ago
Nick Fagerlund	054fdf93cf	Publicize Cloud's token and organization fields Sorry... I need them.	2 years ago
Nick Fagerlund	4ec407af08	Disallow saved cloud plans in VCS workspaces By convention, Terraform Cloud workspaces connected to a VCS repo should should only apply configs that come from the designated branch, to ensure that version control remains the source of truth for that infrastructure. The cloud version of `terraform apply` already includes a guardrail for that, but we forgot to include an equivalent one for `terraform plan` when performing saved plans (which can be applied later, unlike a purely speculative plan). We suspect that TFC actually needs some additional formal access controls around assigning configuration versions to workspaces, as everyone tends to be surprised to learn that the API doesn't actually prevent this. But in the meantime, what's good for the goose (apply command) is good for the gander (plan command), so I'm copying over the check to voluntarily enforce the VCS workflow for plans that can be applied.	2 years ago
Brandon Croft	6500b7c740	change visibility of cloud.Backend Hostname field	3 years ago
hashicorp-copywrite[bot]	53c34ff49c	Update copyright file headers to BUSL-1.1	3 years ago
Brandon Croft	b1d4f18a9b	Create provisional configuration version when saving cloud plan	3 years ago
Nick Fagerlund	2a08a5b46e	Cloud: Split private `readRedactedPlan` func into two Since `terraform show -json` needs to get a raw hunk of json bytes and sling it right back out again, it's going to be more convenient if plain `show` can ALSO take in raw json. In order for that to happen, I need a function that basically acts like `client.Plans.ReadJSONOutput()`, without eagerly unmarshalling that `jsonformat.Plan` struct. As a slight bonus, this also lets us make the tfe client mocks slightly stupider.	3 years ago
Nick Fagerlund	da963a13b9	Implement plan -out for Cloud - Don't save errored plans. - Call op.View.PlanNextStep for terraform plan in cloud mode (We never used to show this footer, because we didn't support -out.) - Create non-speculative config version if saving plan - Rewrite TestCloud_planWithPath to expect success!	3 years ago
kmoe	5900d1177c	cloud: assert import block compatibility (#33282 ) * cloud: assert import block compatibility * check for import <> TFC compatibility during init * imports are not in alphabetical order 🙃 --------- Co-authored-by: CJ Horton <cjhorton@hashicorp.com>	3 years ago
CJ Horton	6ca13bfc1e	fix static check errors	3 years ago
CJ Horton	cdce4c4a6d	write generated config when using the cloud integration	3 years ago
hashicorp-copywrite[bot]	325d18262e	[COMPLIANCE] Add Copyright and License Headers	3 years ago
Glenn Sarti	7e2e834aff	Emit warnings for certain run events in cloud backend (#33020 ) The cloud backend, which communicates with TFC like APIs, can create runs which may have one more configuration parameters altered. These alterations are emitted as run-events on the run so that API clients can consume and display them to users. This commit adds a step in plan operation to query the run-events once a run is created and then emit specific run-event descriptions to the console as warnings for the user.	3 years ago
Sebastian Rivera	5634ae3e18	Unit tests to ensure renderer is appropriately called	3 years ago
Sebastian Rivera	b23cfaefe8	Refactor SRO check to prevent duplicate plan output	3 years ago
Sebastian Rivera	71dac9bf5e	Add token field to cloud backend	3 years ago
Sebastian Rivera	de574ae6d4	Initial implementation of structured logging in cloud backend (#32504 ) * Implementation of structured logging. These are the changes that enable the cloud backend to consume structured logs and make use of the new plan renderer. This will enable CLI-driven runs to view the structured output in the Terraform Cloud UI. * Cloud structured logging unit tests * Remove deferred logs logic, fix minor issues Color formatting fixes, log type stop lists, default behavior for logs that are unknown * Use service disco path in redacted plan url	3 years ago
sivchari	ef4798de8e	fix: pre allocate for composite literal	3 years ago
Glenn Sarti	18da2f0213	Refactor task stage retrieval in cloud backend Previously all of the logic to retrieve Task Stages was in the backend_plan.go file. This commit: * Moves the logic to the backend_taskStages.go file. * Replaces using an array to a map indexed by the Task Stage's stage. This makes it easier to find the relevant stage in the list and means the getTaskStageIDByName function is no longer required.	4 years ago
Glenn Sarti	8562f8a744	Add Pre-Plan Run Tasks to Terraform CLI Prevously the cloud backend would only render post-plan run tasks. Now that pre-plan tasks are in beta, this commit updates the plan phase to render pre-plan run tasks. This commit also moves some common code to the common backend as it will be used by other task stages in the future.	4 years ago
Luces Huayhuaca	bdc7d8c0a1	Upgrade go-tfe dependency to use 1.0 version. It contains breaking changes, so we are updating method signatures, method names and the type of optional parameters, as needed. (#30626 )	4 years ago
Sebastian Rivera	126d6df088	Added run task support for post plan run stage, removed pre apply This commit stems from the change to make post plan the default run task stage, at the time of this commit's writing! Since pre apply is under internal revision, we have removed the block that polls the pre apply stage until the team decides to re-add support for pre apply run tasks.	4 years ago
uturunku1	383da4893b	use new enum string for task stages	4 years ago
Brandon Croft	aa0dda81b4	Fall back to reading latest run without task_stages Older versions of TFE will not allow "task_stages" as an include parameter. In this case, fall back to reading the Run without additional options.	4 years ago
uturunku1	77946af472	pull latest changes from go-tfe branch and use use new field name that previously was incorrectly named TaskStage	4 years ago
uturunku1	8090b23db7	delete unused function	4 years ago
Brandon Croft	0b8bb29a61	[cloud] refactor integration context and add code documentation	4 years ago
Brandon Croft	791c36c504	[cloud] report run tasks by name instead of assuming pre_apply	4 years ago
Brandon Croft	2938ec43fa	[cloud] handle unreachable run tasks	4 years ago
uturunku1	3e9ae69a12	[cloud] run tasks integration This change will await the completion of pre-apply run tasks if they exist on a run and then report the results. It also adds an abstraction when interacting with cloud integrations such as policy checking and cost estimation that simplify and unify output, although I did not go so far as to refactor those callers to use it yet.	4 years ago
Barrett Clark	edbc84420c	Run apply -refresh-state instead of refresh When a user runs `terraform refresh` we give them an error message that tells them to run `terraform apply -refresh-state`. We could just run that command for them, though. That is what this PR does.	5 years ago
Omar Ismail	dd856f8a1b	Add run variables to cloud plan operations from non-file sources Run variables allow the run API to accept input variables not found in the configuration slug (the file-based ones plus workspace vars)	5 years ago
Chris Arcand	7cc53fe163	cloud: Set minimum TFE version These changes remove all of the preexisting version checking for individual features, wiping the slate clean with an overall minimum requirement of a future TFP-API-Version 2.5, which at the time of this writing is expected to be TFE v202112-1. It also actually provides that expected TFE version as an actionable error message, rather than generically saying that it isn't supported or using the somewhat opaque API version header.	5 years ago
Omar Ismail	a387af6c61	Add auto-approve logic, e2e tests	5 years ago
Omar Ismail	594a390f84	Use context parallelism	5 years ago
Chris Arcand	a5f063625a	Replace generic host error messages for feature support	5 years ago
Chris Arcand	ea8ad0b15a	Initial commit of 'cloud' package The cloud package intends to implement a new integration for Terraform Cloud/Enterprise. The purpose of this integration is to better support TFC users; it will shed some overly generic UX and architecture, behavior changes that are otherwise backwards incompatible in the remote backend, and technical debt - all of which are vestiges from before Terraform Cloud existed. This initial commit is largely a porting of the existing 'remote' backend, which will serve as an underlying implementation detail and not be a typical user-level backend. This is because to re-implement the literal backend interface is orthogonal to the purpose of this integration, and can always be migrated away from later. As this backend is considered an implementation detail, it will not be registered as a declarable backend. Within these changes it is, for easy of initial development and a clean diff.	5 years ago

43 Commits (ecfbdaf18d97fec6d019acdb5bbb194f12ecfe92)