25 Commits (2bd3c26fb11bd3d51cdf364c78f36ba767956475)

Author	SHA1	Message	Date
clint shryock	87bb691800	Revert "New provider arukas (#10862)" ... This reverts commit 9176bd4861. This provider includes a dependency that at time of writing requires a *nix system, and will not build on Windows.	9 years ago
Kazumichi Yamamoto	9176bd4861	New provider arukas (#10862) ... * Add a Arukas provider * Add dependencies for the Arukas provider * Add documents for the Arukas	9 years ago
Tom Harvey	05d00a93ce	New Provider: OpsGenie (#11012) ... * Importing the OpsGenie SDK * Adding the goreq dependency * Initial commit of the OpsGenie / User provider * Refactoring to return a single client * Adding an import test / fixing a copy/paste error * Adding support for OpsGenie docs * Scaffolding the user documentation for OpsGenie * Adding a TODO * Adding the User data source * Documentation for OpsGenie * Adding OpsGenie to the internal plugin list * Adding support for Teams * Documentation for OpsGenie Team's * Validation for Teams * Removing Description for now * Optional fields for a User: Locale/Timezone * Removing an implemented TODO * Running makefmt * Downloading about half the internet Someone witty might simply sign this commit with "npm install" * Adding validation to the user object * Fixing the docs * Adding a test creating multple users * Prompting for the API Key if it's not specified * Added a test for multiple users / requested changes * Fixing the linting	9 years ago
Máximo Cuadros	85f0fba9f9	Ignition provider (#6189) ... * providers: ignition, basic config, version and config * providers: ignition, user and passwd example, general cache implementation * vendor: Capture new dependency upstream-pkg * providers: ignition ignition_user * providers: ignition ignition_disk, ignition_group and ignition_raid * providers: ignition_file and ignition_filesystem * providers: ignition_systemd_unit and ignition_networkd_unit * providers: ignition_config improvements * vendor: Capture new dependency upstream-pkg * providers: ignition main * documentation: ignition provider * providers: ignition minor changes * providers: ignition, fix test * fixing tests and latest versions	9 years ago
Paul Tyng	3dfe5a47f1	provider/newrelic: Add new provider for New Relic	9 years ago
Len Smith	015e96d0dd	Initial check in for Icinga2 Provider/Resource (#8306) ... * Initial checkin for PR request * Added an argument to provider to allow control over whether or not TLS Certs will skip verification. Controllable via provider or env variable being set * Initial check-in to use refactored module * Checkin of very MVP for creating/deleting host test which works and validates basic host creation and deletion * Check in with support for creating hosts with variables working * Checking in work to date * Remove code that causes travis CI to fail while I debug * Adjust create to accept multivale * Back on track. Working basic tests. go-icinga2-api needs more test too * Squashing * Back on track. Working basic tests. go-icinga2-api needs more test too * Check in refactored hostgroup support * Check in refactored check_command, hosts, and hsotgroup with a few test * Checking in service code * Add in dependency for icinga2 provider * Add documentation. Refactor, fix and extend based on feedback from Hashicorp * Added checking and validation around invalid URL and unavailable server	9 years ago
Martin Atkins	e772b45970	"external" data source, for integrating with external programs (#8768) ... * "external" provider for gluing in external logic This provider will become a bit of glue to help people interface external programs with Terraform without writing a full Terraform provider. It will be nowhere near as capable as a first-class provider, but is intended as a light-touch way to integrate some pre-existing or custom system into Terraform. * Unit test for the "resourceProvider" utility function This small function determines the dependable name of a provider for a given resource name and optional provider alias. It's simple but it's a key part of how resource nodes get connected to provider nodes so worth specifying the intended behavior in the form of a test. * Allow a provider to export a resource with the provider's name If a provider only implements one resource of each type (managed vs. data) then it can be reasonable for the resource names to exactly match the provider name, if the provider name is descriptive enough for the purpose of the each resource to be obvious. * provider/external: data source A data source that executes a child process, expecting it to support a particular gateway protocol, and exports its result. This can be used as a straightforward way to retrieve data from sources that Terraform doesn't natively support.. * website: documentation for the "external" provider	9 years ago
John Engelman	243ecf3b4f	[Provider] Rancher (#9173) ... * Vendor Rancher Go library. * Implement Rancher Provider. Starting implementation taken from https://github.com/platanus/terraform-provider-rancher Commits from jidonoso@gmail.com and raphael.pinson@camptocamp.com	9 years ago
Mitchell Hashimoto	fd498fbfff	Merge pull request #9538 from hashicorp/f-nomad-provider ... provider/nomad: Nomad provider for managing jobs	9 years ago
Martin Atkins	b2b5831205	"vault" provider registration ... To reduce the risk of secret exposure via Terraform state and log output, we default to creating a relatively-short-lived token (20 minutes) such that Vault can, where possible, automatically revoke any retrieved secrets shortly after Terraform has finished running. This has some implications for usage of this provider that will be spelled out in more detail in the docs that will be added in a later commit, but the most significant implication is that a plan created by "terraform plan" that includes secrets leased from Vault must be *applied* before the lease period expires to ensure that the issued secrets remain valid. No resources yet. They will follow in subsequent commits.	10 years ago
Mitchell Hashimoto	bb5f6498e2	provider/nomad	10 years ago
Alexander Hellbom	d02067a75e	Add PagerDuty provider	10 years ago
stack72	a2970e631c	Merge branch 'cwood/bitbucket-provider' of https://github.com/cwood/terraform into cwood-cwood/bitbucket-provider	10 years ago
Joe Topjian	c2469c95f4	provider/rabbitmq: Initial Commit of RabbitMQ Provider ... Contains provider configuration, a rabbitmq_vhost resource, and acceptance test.	10 years ago
James Nugent	e181d753fe	build: Fix ordering of plugin list	10 years ago
Colin Wood	bd9ddff0cc	Bitbucket provider for terraform	10 years ago
Brad Sickles	70cadcf31d	Implement archive provider and "archive_file" resource. (#7322)	10 years ago
Raphael Randschau	9081cabd6e	Add scaleway provider (#7331) ... * Add scaleway provider this PR allows the entire scaleway stack to be managed with terraform example usage looks like this: ``` provider "scaleway" { api_key = "snap" organization = "snip" } resource "scaleway_ip" "base" { server = "${scaleway_server.base.id}" } resource "scaleway_server" "base" { name = "test" # ubuntu 14.04 image = "aecaed73-51a5-4439-a127-6d8229847145" type = "C2S" } resource "scaleway_volume" "test" { name = "test" size_in_gb = 20 type = "l_ssd" } resource "scaleway_volume_attachment" "test" { server = "${scaleway_server.base.id}" volume = "${scaleway_volume.test.id}" } resource "scaleway_security_group" "base" { name = "public" description = "public gateway" } resource "scaleway_security_group_rule" "http-ingress" { security_group = "${scaleway_security_group.base.id}" action = "accept" direction = "inbound" ip_range = "0.0.0.0/0" protocol = "TCP" port = 80 } resource "scaleway_security_group_rule" "http-egress" { security_group = "${scaleway_security_group.base.id}" action = "accept" direction = "outbound" ip_range = "0.0.0.0/0" protocol = "TCP" port = 80 } ``` Note that volume attachments require the server to be stopped, which can lead to downtimes of you attach new volumes to already used servers * Update IP read to handle 404 gracefully * Read back resource on update * Ensure IP detachment works as expected Sadly this is not part of the official scaleway api just yet * Adjust detachIP helper based on feedback from @QuentinPerez in https://github.com/scaleway/scaleway-cli/pull/378 * Cleanup documentation * Rename api_key to access_key following @stack72 suggestion and rename the provider api_key for more clarity * Make tests less chatty by using custom logger	10 years ago
Derek Abdine	7bdc060d24	provider/logentries: Implementing logentries provider (#7067) ... * logentries provider * logentries vendoring * logentries docs	10 years ago
James Nugent	5a0f6565d3	Merge pull request #6672 from apparentlymart/random-provider ... Logical Resources for Random Values	10 years ago
James Nugent	28ad394264	build: Update generated internal plugin list	10 years ago
Martin Atkins	3e34ddbf38	New "random" provider, representing randomness ... This provider will have logical resources that allow Terraform to "manage" randomness as a resource, producing random numbers on create and then retaining the outcome in the state so that it will remain consistent until something explicitly triggers generating new values. Managing randomness in this way allows configurations to do things like random distributions and ids without causing "perma-diffs".	10 years ago
James Nugent	9d77e0af6c	core: Add new providers to internal list	10 years ago
James Nugent	991dc3f86f	core: Add Cobbler provider to internal plugin list	10 years ago
Chris Bednarski	6360e6c8b6	Implemented internal plugin calls; which allows us to compile plugins into the main terraform binary	10 years ago