terraform

Commit Graph

Author	SHA1	Message	Date
Liam Cervante	37b88b33ce	Rollout equivalence testing during Terraform releases and builds (#31928 ) * add some basic equivalence tests and execute them in the build pipeline * remove old file, now unused * update terraform-equivalence-testing to v0.2.0 * add separate action * make sure to read from hashicorp repo * remove elevated github token where possible * Don't need elevated token anymore * update with official mock provider * last change: don't need the authorization header for public repositories.	3 years ago
Craig Wright	3b8e97c38c	Update CONTRIBUTING.md Removing the statement which does not reflect the current status for reviews of community-contributed pull requests.	4 years ago
Craig Wright	ae4a8ba77b	Fixing a bug introduced in the review process.	4 years ago
Craig Wright	1650bb9892	Merge pull request #31951 from hashicorp/docs-issue-form Add Documentation Issue form template	4 years ago
Craig Wright	d40b5c7755	Update .github/ISSUE_TEMPLATE/documentation_issue.yml Co-authored-by: Judith Malnick <judith.patudith@gmail.com>	4 years ago
Craig Wright	a8d6d5c913	Correcting a line break visual issue.	4 years ago
Craig Wright	b1c720a633	Update .github/ISSUE_TEMPLATE/documentation_issue.yml Thanks! Co-authored-by: Judith Malnick <judith.patudith@gmail.com>	4 years ago
Craig Wright	f058392421	Apply suggestions from code review Thanks! Co-authored-by: Judith Malnick <judith.patudith@gmail.com>	4 years ago
Liam Cervante	4d7ba14f72	Add skeleton action for equivalence tests (#31940 )	4 years ago
Craig Wright	3afa9bd08e	Create documentation_issue.yml Closes https://github.com/hashicorp/terraform/issues/31552. Adds a new issue form type for documentation issues. Format discussed with docs team.	4 years ago
Alisdair McDiarmid	3ff89c9cec	Update pull_request_template.md	4 years ago
Alisdair McDiarmid	99fcb747e9	Revise markup to avoid unwanted checklist UI	4 years ago
Alisdair McDiarmid	6c75e54681	Add initial pull request template This is intended to add some structure to pull request descriptions, and encourage peer review of changelog entries before merging a PR.	4 years ago
Martin Atkins	d735de3656	build: checks.yml GitHub Actions workflow doesn't need goimports installed The importscheck script now uses "go run" to run this program and so the Go toolchain will install it automatically using the version number of golang.org/x/tools specified in our go.mod file.	4 years ago
Craig Wright	a63a2e3ec8	Minor copy fixes for the issue form title reminder text.	4 years ago
Craig Wright	9ca1b18988	Fixing placeholder values, adding usage note to bottom of the form.	4 years ago
Craig Wright	dc0f196cbb	Merge pull request #31651 from hashicorp/issue-forms Migrating from Markdown to Form style Github issues.	4 years ago
Craig Wright	95c133f2ec	Modifying the version input to use shell rendering. This simplifies entry for the user, no longer requiring markdown formatting wrappers.	4 years ago
Alvin Huang	634c875bea	set PRODUCT_VERSION for default docker build	4 years ago
Craig Wright	aba0ac0fae	Migrating from Markdown to Form style Github issues. The goal of this change is to simplify the process of filing issues with hashicorp/terraform. In the previous Markdown syntax, the instructions tended to get washed out in a sea of comment markers. The new Github Form Issues breaks each section into a form element, with instructions printed clearly as HTML in the page. We are further hoping to guide users to the correct repository when filing provider issues, or the community forums when asking usage questions.	4 years ago
Liam Cervante	afd273d636	Add goimports as a check to the Github commit actions (#31432 ) * Add goimports as a check to the Github commit actions * check diff against main instead of last commit * goimports should fix the problems * fix up conditionals and wildcard matching * specify origin/main in diff * fetch main branch when checkout * back to origin main	4 years ago
Martin Atkins	284a38a04c	build: Accept version numbers with prereleases containing dashes Previously we'd discard everything after the second dash.	4 years ago
Martin Atkins	096f0dc0da	build: Write the detected version number into the generated executable This also sets an additional variable if it detects that this is an alpha or development build, which currently does nothing but might eventually turn on the ability to use experimental features, if we make that something available only in prereleases.	4 years ago
Martin Atkins	7dd3cdfab4	build: Fetch all tags before deciding which version we're building The actions/checkout workflow does some heroics to try to fetch exactly the commit being built and nothing else, even if asked to fetch the history leading up to that commit. That means we don't end up having enough information to get an accurate answer from "git describe". Since we're intentionally relying on the git history here, we'll fetch all of the tags explicitly after initial checkout. Although that does add some delay to this step, we're intentionally doing this version calculation only once as a separate workflow job so that all of the other jobs can still benefit from this action's quicker checkout behavior.	4 years ago
James Bardin	2bd72914d8	add internal/states to the race detector tests This runs relatively quickly, and there is at least 1 test with concurrent operations.	4 years ago
Claire Labry	dd2decf921	change action to pull v1 instead of main	4 years ago
James Bardin	0693c8dfe7	enable the race detector in tests	4 years ago
Martin Atkins	5b615882e2	build: "Quick Checks" to run for external contributions The "push" event is only for pushes to branches within the same repository. Since external contributors make commits in their own repositories rather than directly in the target repository, we also need the pull_request event to react to opening a pull request and to pushing new code to an external branch associated with a pull request. Since internal pull requests would in principle trigger both "push" _and_ "pull_request", we also constrain the push event only to the branches we typically release from, on the assumption that all other branches will merge into those via pull requests. This avoids redundantly running the same checks in response to two events at the same time.	4 years ago
Martin Atkins	bbf540e0e3	build: "Quick Checks" caches protoc between runs Building our protobuf files requires the protoc tool, which takes a little while to download and install. Hopefully downloading it out of the GitHub Actions cache will make it a little faster in the common case where we're still using the same version as the previous run.	4 years ago
Martin Atkins	42a618f7c1	build: "Quick Checks" runs consistency checks concurrently with others Originally we had this running as part of the Unit Tests job because most of the checks are relatively fast. However, the addition of the protobuf generation check made that no longer be true because it needs to download and run protoc. With that extra overhead it now _is_ productive to spend the time booting and installing Go on third worker, as long as GitHub Actions continues to let us run all three of these jobs concurrently most of the time.	4 years ago
Martin Atkins	95f26b340b	build: "Quick Checks" no longer uses goenv goenv was making things more complicated than needed since it's really designed to help with interactive use in a shell more than automated use like this. Instead, we'll follow the same strategy that our build.yml was doing of just reading the .go-version file directly and then using the official actions/setup-go action to do the actual installation. The key advantage here is that Go ends up installed in a way where just running "go" will do the right thing, and we no longer need to fuss with shims and version-based path prefixes. Rather than duplicating the logic from build.yml, instead it's factored out into a separate composite action which both build.yml and checks.yml will now share, in case we want to change the Go version selection methodology in the future.	4 years ago
Martin Atkins	67fedd48a6	build: "Quick Checks" avoid repeating Install Go This factors out the "Install Go" step into a separate composite action which we can then call from both of the jobs that need it. We can't factor out the "Cache Go Modules" because GitHub doesn't allow composite actions to refer to other external actions.	4 years ago
Martin Atkins	9210ce6cdd	build: GitHub Actions "Quick Checks" workflow This is intended to eventually replace the CircleCI-based checks we use as part of the PR process in this repository. We're already using GitHub Actions for various other processes in this repository, so this change is motivated by consistency of having all of our automation running in the same system and written in the same language. This is not a complete replacement for our CircleCI workflow yet, and probably won't ever be because the CircleCI workflow contains some steps that are arguably redundant with other processes we follow elsewhere. However, the CircleCI workflow remains for now and won't be removed until we're satisfied that enough of it is replicated by this GitHub Actions workflow.	4 years ago
Laura Pacilio	2a3b0f9c1e	Merge pull request #30017 from RubyElders/internal-contributing-docs Update go test commands in .github/CONTRIBUTING.md.	4 years ago
Alisdair McDiarmid	636499830b	Add merged pull request reminder	4 years ago
Katy Moe	eaf748f24d	remove dependabot	4 years ago
Michele Degges	2f465e6047	Update packaging action name	4 years ago
Martin Atkins	4ec1feaa3d	build: CGO_ENABLED when building for macOS Normally when we cross-compile we do so without CGo, because we don't have suitable C headers available for systems other than the host. However, building for macOS on macOS is special because there are sufficient headers available on darwin_amd64 to build for both darwin_amd64 _and_ darwin_arm64. Also, we _must_ use CGo on macOS because the system resolver is only available via darwin's libc, and so building without CGo produces executables that don't resolve hostnames correctly. This is a conditional in bash to avoid having to duplicate the entire step. Perhaps later we'll find a more general version of this which can avoid the special case, but this is sufficient for the moment.	4 years ago
Martin Atkins	28a6036cf2	build: Separate Linux distro package builds into separate job In our build workflow we'll treat Linux distribution packaging (currently .deb and .rpm packages) as a separate job, instead of embedding it into the "build" job, so that this step can happen concurrently with the other derived actions like the docker image build, and the e2etest runs.	4 years ago
Martin Atkins	c1699ea80c	build: Constrain permissions for the "build" workflow steps This workflow only generates artifacts and doesn't need to modify anything about the repository.	4 years ago
Martin Atkins	3bf758eaf5	build: Consolidate build-darwin job into just "build" We can use an extra matrix dimension to select which execution environment we'll use for each GOOS/GOARCH pair, and thus avoid duplicating the job definition for darwin just to set runs-on: macos-latest for it. This is not really an intended use of a matrix dimension because it's directly related to the existing "goos" one, rather than being an independent third dimension, but it doesn't matter in practice because we're using the "include" option to specify exact combinations, and thus we're not relying on the built-in functionality to generate all possible matrix combinations.	4 years ago
Martin Atkins	218e55b23c	build: Build docs source package as part of the release pipeline This should eventually grow to be a step that actually verifies the validity of the docs source prior to publishing the artifact that a downstream publishing pipeline can consume, but for the moment it's really just a placeholder since we have no such validation step and no downstream pipeline consuming this artifact. The general idea here is that the artifacts from this workflow should be sufficient for all downstream release steps to occur without any direct access to the Terraform CLI repository, and so this is intended to eventually meet that ideal but as of this commit the website docs publishing step _does_ still depend on direct access to this repository.	4 years ago
Martin Atkins	b802db75d7	build: Build and run e2etest as part of the release build pipeline This uses the decoupled build and run strategy to run the e2etests so that we can arrange to run the tests against the real release packages produced elsewhere in this workflow, rather than ones generated just in time by the test harness. The modifications to make-archive.sh here make it more consistent with its originally-intended purpose of producing a harness for testing "real" release executables. Our earlier compromise of making it include its own terraform executable came from a desire to use that script as part of manual cross-platform testing when we weren't yet set up to support automation of those tests as we're doing here. That does mean, however, that the terraform-e2etest package content must be combined with content from a terraform release package in order to produce a valid contest for running the tests. We use a single job to cross-compile the test harness for all of the supported platforms, because that build is relatively fast and so not worth the overhead of matrix build, but then use a matrix build to actually run the tests so that we can run them in a worker matching the target platform. We currently have access only to amd64 (x64) runners in GitHub Actions and so for the moment this process is limited only to the subset of our supported platforms which use that architecture.	4 years ago
Martin Atkins	6704f8c795	Initial work on a new package build process For the moment this is just an experimental additional sidecar package build process, separate from the one we really use for releases, so that we can get some experience building in the GitHub Actions environment before hopefully eventually switching to using the artifacts from this process as the packages we'll release through the official release channels. It will react to any push to one of our release branches or to a release tag by building official-release-like .zip, .deb, and .rpm packages, along with Docker images, based on the content of the corresponding commit. For the moment this doesn't actually produce _shippable_ packages because in particular it doesn't know how to update our version/version.go file to hard-code the correct version number. Once Go 1.18 is release and we've upgraded to it we'll switch to using debug.ReadBuildInfo to determine our version number at runtime and so no longer need to directly update a source file for each release, but that functionality isn't yet available in our current Go 1.17 release.	4 years ago
Josef Šimánek	ffcb167bce	Update go test commands in .github/CONTRIBUTING.md.	4 years ago
James Bardin	91f27c6d04	remove Crash section of issue template Terraform is no longer going to silently capture all logs for a possible crash report, and therefor won't create a crash.log file when a panic is encountered. The prompt to create a log file with TF_LOG from the Debug Output section should suffice to get users to submit the logs when possible. In the case of a crash specifically, the crash output also requests that the stack trace be added to the issue for users who may not be aware of what is necessary.	5 years ago
Paul Hinze	ad634f60a5	Add clarification to message about community PR review	5 years ago
Martin Atkins	6562466c32	Be explicit that community PR review is currently paused	5 years ago
Radek Simko	abc762c42d	docs: Update outdated info about terraform-providers org (#29328 ) * docs: Update outdated info about terraform-providers org * Remove codecov mentions	5 years ago
Kent 'picat' Gruber	fc63c1949d	Merge pull request #29215 from hashicorp/configure-dependabot Add initial Dependabot configuration	5 years ago
James Bardin	c449148d8c	update GH issue template Change generic provider link to the registry, since the majority of providers are no longer under the terraform-provider org. Remove example link to an individual user's repo.	5 years ago
Kent 'picat' Gruber	4291916f0f	Add initial dependabot configuration	5 years ago
Chris Arcand	c556a0c9c9	mailto is not supported in GitHub template URLs	5 years ago
Chris Arcand	e3b9ab4891	Add support email for TFC-related issues	5 years ago
Brian Flad	4b25a07bc7	Remove GitHub HashiBot configuration For the `closed_issue_locker` behavior, this is a migration to an equivalent action. For the `label_issue_migrater` behavior, this is not replaced and instead it is suggested to use native GitHub functionality for issue transfer. If mostly equivalent behavior is desired via label automation, it may be possible to submit an issue transfer feature request to dessant/label-actions as it is a popular community action or create a new GitHub Action. Please reach out if this is a major issue for your team. For the `remove_labels_on_reply` behavior, it is equivalent except this initial configuration does not make the collaborators distinction. There is a workflow configuration workaround for setting up per-user ignores for any job/step, so if you desire that here please reach out.	5 years ago
Kristin Laemmert	106bcd3bf0	update to match new default branch name (#27909 )	5 years ago
Jonathan Hall	49ee3d3ef8	Grammar nit: "setup" as a verb should be spelled "set up"	5 years ago
Alisdair McDiarmid	3ed08e3566	Remove backport review teams for now This requires more GitHub token permissions than we have, and it's inessential. The backport PRs should have reviews assigned to the original PR author anyway.	6 years ago
Alisdair McDiarmid	13d70844d7	Upgrade backport-assistant	6 years ago
Alisdair McDiarmid	61b38f3ada	Another action regex fix attempt This time I actually tested the regex	6 years ago
Alisdair McDiarmid	e65f427927	Try to fix backport action I made a mistake editing the regex. Here's hoping this works!	6 years ago
Alisdair McDiarmid	1e32354e3e	Fix label regexp We only use two components for versions, e.g. `0.13-backport` -> `v0.13`	6 years ago
Alisdair McDiarmid	fd14b237e5	Add backport assistant Based on documentation in https://github.com/hashicorp/backport-assistant, using a token from the teamterraform user.	6 years ago
Petros Kolyvas	dc48450e79	Provisioner contribution guide updates (#26538 ) An update on the deprecated state of vendor provisioners for our contribution guide.	6 years ago
Daniel Dreier	6211020453	Merge pull request #26247 from hashicorp/danieldreier/bugtriage Add bug triage guide	6 years ago
Daniel Dreier	8af2120e1b	Add bug triage guide Add a written bug triage process and link to it in README.md Bug process Remove goals, edit for brevity, and move how to write a good issue report to bug report template link HashiCorp GPG key in bug report template add summary links for triage process	6 years ago
James Bardin	50e547db4d	remove vendoring from contribution guide	6 years ago
Jamie Finnigan	7eda697978	remove local SECURITY.md in favor of org-wide policy	6 years ago
Daniel Dreier	cc86889fd6	Update GitHub issue templates Add "bug" label to bug_report.md Add "new" label to feature_request.md	6 years ago
Daniel Dreier	237a1f3684	Add "new" label to issue templates	6 years ago
Tom Hummel	7e879e0034	fix .go-version repo link	6 years ago
Pam Selle	d1e9172960	Merge pull request #25292 from mschuchard/patch-1 update hcl language markdown to terraform markdown	6 years ago
Alisdair McDiarmid	8c3648c1e6	terraform version is preferred	6 years ago
Alisdair McDiarmid	7b526b1969	terraform version is preferred	6 years ago
Matt Schuchard	86a511e257	update hcl language markdown to terraform markdown	6 years ago
Daniel Dreier	c14d6f4241	Fix typo in CONTRIBUTING.md	6 years ago
Petros Kolyvas	9d1d8c0212	Merge branch 'contribution-codeowners' of github:pkolyvas/terraform into contribution-codeowners	6 years ago
Petros Kolyvas	02d67b8049	Merge branch 'contribution-codeowners' of github:pkolyvas/terraform into contribution-codeowners	6 years ago
Petros Kolyvas	e760927408	Update .github/CONTRIBUTING.md Co-Authored-By: Pam Selle <pamela.selle@gmail.com>	6 years ago
Petros Kolyvas	e92b8a82f4	Pam & Kristin's feedback & some more suggested changed.	6 years ago
Petros Kolyvas	783c06b6da	Kristin's corrections Co-Authored-By: Kristin Laemmert <mildwonkey@users.noreply.github.com>	6 years ago
Petros Kolyvas	6529a7c6e9	Kristin's comments & suggested changes	6 years ago
Petros Kolyvas	f6ac9e361b	Merge branch 'contribution-codeowners' of github:pkolyvas/terraform into contribution-codeowners	6 years ago
Petros Kolyvas	77ebf266f3	Restored the note about our community guidelines	6 years ago
Petros Kolyvas	6ff988a423	Apply suggestions from code review Alisdair's fixes. Co-Authored-By: Alisdair McDiarmid <alisdair@users.noreply.github.com>	6 years ago
Petros Kolyvas	10437b4b15	Update .github/CONTRIBUTING.md Co-Authored-By: Alisdair McDiarmid <alisdair@users.noreply.github.com>	6 years ago
Petros Kolyvas	ad15e4a116	A few more spacing issues in MD format for GH	6 years ago
Petros Kolyvas	c7cae98076	GitHub hates me	6 years ago
Petros Kolyvas	cd54300621	Why won't you h4 maintainers.	6 years ago
Petros Kolyvas	db5878ff04	More updates and fixes, some grammatical, some clarity issues, one markdown bugaboo	6 years ago
Petros Kolyvas	ca90de14ec	Updated Contribution Guide TOC	6 years ago
Petros Kolyvas	942b4df545	Added a provisioners section and a maintainers section	6 years ago
Petros Kolyvas	61fe0a3402	Fixed an ordering/clarity issue with the TOC	6 years ago
Petros Kolyvas	96e1a1f800	more prescriptive Contributor's guide	6 years ago
Petros Kolyvas	a40207c9eb	Updated contributing to Terraform	6 years ago
Kristin Laemmert	976d2980b2	docs/contributing: add note about codecov (#24434 )	6 years ago
Riccardo Piccoli	094ed0ff4d	spelling fix	6 years ago
Radek Simko	5b5efa2c7e	Update .github/SECURITY.md Co-Authored-By: Kristin Laemmert <mildwonkey@users.noreply.github.com>	6 years ago
Radek Simko	b4a22aa0e9	Make link to vulnerability reports more visible	6 years ago
Radek Simko	211cf08b38	Update config.yml	7 years ago
Radek Simko	438279c520	github: Add issue templates config	7 years ago
Radek Simko	7860f55e4f	Version tools per Go convention under tools.go	7 years ago
Martin Atkins	f96edbb113	Revise our contributing/development documentation Our documentation for how to contribute was in quite a state of disrepair, with some documents still describing things as they were before moving providers into separate repositories, others making assumptions about Go development that are no longer true in modules mode, and so forth. This is an attempt at a reset to a good state that should work with the codebase as it currently stands, and should hopefully serve as a basis for iterative improvement from here. These new instructions lean primarily on standard Go toolchain usage and instruct using the Makefile only for some Terraform-specific situations that the Go toolchain does not automatically handle. The idea here is that this direct usage of primary commands in the Go toolchain is less likely to be broken by changes in future Go releases, and should be immediately familiar to anyone who has experience with Go development.	7 years ago
Pam Selle	d9bf945a14	Small typo fix	7 years ago
Kristin Laemmert	e1d0acda0b	website/contributing: update contribution documentation (#22883 ) * website/contributing: update contribution documentation This PR seeks to remove outdated and incorrect information. There is still work to be done updating the information that's left; this is merely the first step.	7 years ago
Ryan	1a53575b15	build: use correct link for GCP provider in GitHub issue template	7 years ago
Paul Tyng	de6e33dcb0	Update provider_issue.md	7 years ago
Paul Tyng	01e6002101	Update provider_issue.md	7 years ago
Paul Tyng	f49f3e56f4	Create provider_issue.md	7 years ago
Radek Simko	b661a983b8	Add labels to issues templates	7 years ago
Martin Atkins	c97de0b526	Separate issue templates for Bugs vs. Features Here our prior existing single template becomes the "Bug report" template, and we introduce a second "Feature request" template that is more appropriate for gathering context about a feature request.	8 years ago
Martin Atkins	a23bb3bd55	issue template: "additional context" instead of "important factoids" As pointed out in #16987, "factoids" are not really what we're looking for here. The goal of this section is to capture additional context that isn't represented by any of our other section headings, so we'll change this to "Additional Context" to be clearer about what we want here and to avoid a confusing misuse of a quirky English word that not all readers will be familiar with.	8 years ago
Martin Atkins	28632790b7	Issue template: comment out the instruction portions By wrapping the instruction portions in comments we can get a cleaner rendering of the issue if a user posts it without removing the instructions first. The content is otherwise the same as before.	9 years ago
Radek Simko	35553c9ab9	Merge pull request #16491 from hashicorp/radeksimko/coc Create CODE_OF_CONDUCT.md	9 years ago
Radek Simko	4f03de2ec4	Create CODE_OF_CONDUCT.md	9 years ago
Radek Simko	38a4c9a4e0	Create SUPPORT.md	9 years ago
Martin Atkins	c0ce0f3233	Revisions to ISSUE_TEMPLATE.md This is just a few editorial tweaks to the issue template. The primary motivation here was to shorten the section about provider issues now that we're no longer in the transitional state; I suspect that this scary wall of text is dissuading people from actually reading and following the template. Otherwise, this is just some tweaks to the wording and some adjustments for the fact that we're now not expecting provider issues here.	9 years ago
Clint	458cac7f49	Update ISSUE_TEMPLATE (#15222 ) * Update ISSUE_TEMPLATE Update ISSUE_TEMPLATE to direct people to new split providers * Create ISSUE_TEMPLATE.md More loud * Update ISSUE_TEMPLATE.md * Create ISSUE_TEMPLATE.md * Create ISSUE_TEMPLATE.md moved to the top	9 years ago
Jake Champlin	f811c4c16c	documentation: Add OPC to CONTRIBUTING Adds the Oracle OPC provider to the list of Hashicorp Providers in the CONTRIBUTING.md document.	9 years ago
Radek Simko	74129323bd	Mention LOC of incoming PRs in contributors guide (#13737 )	9 years ago
Dan Stine	efeae1ee03	Fix a few typos in contributing guidelines (#10825 )	9 years ago
Simon Westcott	c990e38601	Correct AWS secret key variable name	10 years ago
Justin Clark	c011e1c3f3	Correct grammar in ISSUE_TEMPLATE.md (#6241 )	10 years ago
James Nugent	0b52805427	Unwrap text in issue template This plays more nicely with mobile email clients.	10 years ago
Seth Vargo	cc298b3fbc	Add issue_template (#6017 )	10 years ago

... 2 3 4 5 6

275 Commits (stacks-variable-validations)