terraform

Commit Graph

Author	SHA1	Message	Date
github-actions[bot]	1d06b6d1ac	Backport of fix(cloud): cloud backend rendering query warning diags into v1.14 (#38055 ) * backport of commit `3852fd121a` * backport of commit `042324b81c` * backport of commit `ade20e59a6` * backport of commit `46b5e8582c` * backport of commit `f7d2cccc92` * backport of commit `14290c3687` --------- Co-authored-by: Michael Yocca <michael.yocca@hashicorp.com>	4 months ago
Liam Cervante	74a8d2c6a9	actions: connect invoke flag with TFC (#37544 ) (#37747 ) * actions: connect invoke flag with TFC * use latest go-tfe	7 months ago
Daniel Banck	f6842ce5af	tf query: ready list blocks for beta (#37619 ) (#37630 ) Co-authored-by: Samsondeen <40821565+dsa0x@users.noreply.github.com>	8 months ago
Daniel Banck	1ac8497994	Add support for Terraform Search in the cloud backend (TF-25935) (#37479 )	8 months ago
Sarah French	371e625ea9	Update URLs from `www.terraform.io` to `developer.hashicorp.com` (#36792 ) * Update URLs from www.terraform.io to developer.hashicorp.com * More updates to URLs linking to documentation in documentation and user-facing warnings/errors * More updates to URLs linking to documentation, in docs, code, test fixtures * Replace www.terraform.io/community with link to Community Forum * Apply suggestions from code review Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com> --------- Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com>	1 year ago
Sebastian Rivera	015f795ff0	Rebrand Terraform Cloud to HCP Terraform	2 years ago
Liam Cervante	01c0480e77	Test framework will produce regular updates in -json mode (#33953 ) * Test framework will produce regular updates in -json mode * add tests * docs * docs tweaking	3 years ago
Liam Cervante	ffbcaf8bef	Implement TFC integration for private module registry test runs (#33710 ) * implement module testing via TFC * ready for review * fix static checks * licence headers	3 years ago
Nick Fagerlund	7f6b827987	Modify tfe client mocks to meet some new requirements - Add plausible unredacted plan json for `plan-json-{basic,full}` testdata -- Created by just running the relevant terraform commands locally. - Add plan-json-no-changes testdata -- The unredacted json was organically grown, but I edited the log and redacted json by hand to match what I observed from a real but unrelated planned-and-finished run in TFC. - Add plan-json-basic-no-unredacted testdata -- This mimics a lack of admin permissions, resulting in a 404. - Hook up `MockPlans.ReadJSONOutput` to test fixtures, when present. This method has been implemented for ages, and has had a backing store for unredacted plan json, but has been effectively a no-op since nothing ever fills that backing store. So, when creating a mock plan, make an attempt to read unredacted json and stow it in the mocks on success. - Make it possible to get the entire MockClient for a test backend In order to test some things, I'm going to need to mess with the internal state of runs and plans beyond what the go-tfe client API allows. I could add magic special-casing to the mock API methods, or I could locate the shenanigans next to the test that actually exploits it. The latter seems more comprehensible, but I need access to the full mock client struct in order to mess with its interior. - Fill in some missing expectations around HasChanges when retrieving a run + plan.	3 years ago
Lauren	dcccd3b266	Add error handling and tests for saved plan bookmark load/save (#33268 )	3 years ago
Nick Fagerlund	df7a1c821a	Move SavedPlanBookmark to dedicated `internal/cloud/cloudplan` package Having this sitting loose in `cloud` proved problematic because of circular import dependencies. Putting it in a sub-package under cloud frees us up to reference the type from places like `internal/backend`!	3 years ago
Lauren	717a36036d	codify saved plan artifact contents (#33185 )	3 years ago
CJ Horton	b88bae2ec4	tests for cloud backend config generation	3 years ago
Sebastian Rivera	6d0a191ec4	Handle provisioner log types in renderer	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
Theo Chupp	d15a2bc024	fix: local variables should not be overridden by remote variables during `terraform import` (#29972 ) * fix: local variables should not be overridden by remote variables during `terraform import` * chore: applied the same fix in the 'internal/cloud' package * backport changes from cloud package to remote package Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com> Co-authored-by: uturunku1 <luces.huayhuaca@gmail.com>	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
Chris Arcand	34597c237f	cloud: Don't ignore .log golden files	5 years ago
Chris Arcand	85f37f1aa5	Add missing log mocks I missed adding these in the original porting commit from the remote backend, because *.log is added to gitignore.	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

20 Commits (v1.14)