terraform

Commit Graph

Author	SHA1	Message	Date
Andy Lindeman	85f759f296	Updates google/go-github to the latest revision (#12604 ) * Updates to the latest go-github * `github_repository_collaborator` uses invitations API	9 years ago
Joe Topjian	f4e74650f0	provider/openstack: Set Availability Zone in Instances (#12610 ) * provider/openstack: Set Availability Zone in Instances This commit configures the openstack_compute_instance_v2 resource to set the Availability Zone of the instance resource. * vendor: Updating Gophercloud for OpenStack	9 years ago
Sean Chittenden	17fb98afa2	Circonus Provider (#12338 ) * Begin stubbing out the Circonus provider. * Remove all references to `reverse:secret_key`. This value is dynamically set by the service and unused by Terraform. * Update the `circonus_check` resource. Still a WIP. * Add docs for the `circonus_check` resource. Commit miss, this should have been included in the last commit. * "Fix" serializing check tags I still need to figure out how I can make them order agnostic w/o using a TypeSet. I'm worried that's what I'm going to have to do. * Spike a quick circonus_broker data source. * Convert tags to a Set so the order does not matter. * Add a `circonus_account` data source. * Correctly spell account. Pointed out by: @postwait * Add the `circonus_contact_group` resource. * Push descriptions into their own file in order to reduce the busyness of the schema when reviewing code. * Rename `circonus_broker` and `broker` to `circonus_collector` and `collector`, respectively. Change made with concent by Circonus to reduce confusion (@postwait, @maier, and several others). * Use upstream contsants where available. * Import the latest circonus-gometrics. * Move to using a Set of collectors vs a list attached to a single attribute. * Rename "cid" to "id" in the circonus_account data source and elsewhere where possible. * Inject a tag automatically. Update gometrics. * Checkpoint `circonus_metric` resource. * Enable provider-level auto-tagging. This is disabled by default. * Rearrange metric. This is an experimental "style" of a provider. We'll see. That moment. When you think you've gone off the rails on a mad scientist experiment but like the outcome and think you may be onto something but haven't proven it to yourself or anyone else yet? That. That exact feeling of semi-confidence while being alone in the wilderness. Please let this not be the Terraform provider equivalent of DJB's C style of coding. We'll know in another resource or two if this was a horrible mistake or not. * Begin moving `resource_circonus_check` over to the new world order/structure: Much of this is WIP and incomplete, but here is the new supported structure: ``` variable "used_metric_name" { default = "_usage`0`_used" } resource "circonus_check" "usage" { # collectors = ["${var.collectors}"] collector { id = "${var.collectors[0]}" } name = "${var.check_name}" notes = "${var.notes}" json { url = "https://${var.target}/account/current" http_headers = { "Accept" = "application/json" "X-Circonus-App-Name" = "TerraformCheck" "X-Circonus-Auth-Token" = "${var.api_token}" } } stream { name = "${circonus_metric.used.name}" tags = "${circonus_metric.used.tags}" type = "${circonus_metric.used.type}" } tags = { source = "circonus" } } resource "circonus_metric" "used" { name = "${var.used_metric_name}" tags = { source = "circonus" } type = "numeric" } ``` * Document the `circonus_metric` resource. * Updated `circonus_check` docs. * If a port was present, automatically set it in the Config. * Alpha sort the check parameters now that they've been renamed. * Fix a handful of panics as a result of the schema changing. * Move back to a `TypeSet` for tags. After a stint with `TypeMap`, move back to `TypeSet`. A set of strings seems to match the API the best. The `map` type was convenient because it reduced the amount of boilerplate, but you loose out on other things. For instance, tags come in the form of `category:value`, so naturally it seems like you could use a map, but you can't without severe loss of functionality because assigning two values to the same category is common. And you can't normalize map input or suppress the output correctly (this was eventually what broke the camel's back). I tried an experiment of normalizing the input to be `category:value` as the key in the map and a value of `""`, but... seee diff suppress. In this case, simple is good. While here bring some cleanups to _Metric since that was my initial testing target. * Rename `providerConfig` to `_ProviderConfig` * Checkpoint the `json` check type. * Fix a few residual issues re: missing descriptions. * Rename `validateRegexp` to `_ValidateRegexp` * Use tags as real sets, not just a slice of strings. * Move the DiffSuppressFunc for tags down to the Elem. * Fix up unit tests to chase the updated, default hasher function being used. * Remove `Computed` attribute from `TypeSet` objects. This fixes a pile of issues re: update that I was having. * Rename functions. `GetStringOk` -> `GetStringOK` `GetSetAsListOk` -> `GetSetAsListOK` `GetIntOk` -> `GetIntOK` * Various small cleanups and comments rolled into a single commit. * Add a `postgresql` check type for the `circonus_check` resource. * Rename various validator functions to be _CapitalCase vs capitalCase. * Err... finish the validator renames. * Add `GetFloat64()` support. * Add `icmp_ping` check type support. * Catch up to the _APIAttr renames. Deliberately left out of the previous commit in order to create a clean example of what is required to add a new check type to the `circonus_check` resource. Clarify when the `target` attribute is required for the `postgresql` check type. * Correctly pull the metric ID attribute from the right location. * Add a circonus_stream_group resource (a.k.a. a Circonus "metric cluster") * Add support for the [`caql`](https://login.circonus.com/user/docs/caql_reference) check type. * Add support for the `http` check type. * `s/SSL/TLS/g` * Add support for `tcp` check types. * Enumerate the available metrics that are supported for each check type. * Add [`cloudwatch`](https://login.circonus.com/user/docs/Data/CheckTypes/CloudWatch) check type support. * Add a `circonus_trigger` resource (a.k.a Circonus Ruleset). * Rename a handful of functions to make it clear in the function name the direction of flow for information moving through the provider. TL;DR: Replace `parse` and `read` with "foo to bar"-like names. * Fix the attribute name used in a validator. Absent != After. * Set the minimum `absent` predicate to 70s per testing. * Fix the regression tests for circonus_trigger now that absent has a 70s min * Fix up the `tcp` check to require a `host` attribute. Fix tests. It's clear I didn't run these before committing/pushing the `tcp` check last time. * Fix `circonus_check` for `cloudwatch` checks. * Rename `parsePerCheckTypeConfig()` to `_CheckConfigToAPI` to be consistent with other function names. grep(1)ability of code++ * Slack buttons as an integer are string encoded. * Fix updates for `circonus_contact`. * Fix the out parameters for contact groups. * Move to using `_CastSchemaToTF()` where appropriate. * Fix circonus_contact_group. Updates work as expected now. * Use `_StateSet()` in place of `d.Set()` everywhere. * Make a quick pass over the collector datasource to modernize its style * Quick pass for items identified by `golint`. * Fix up collectors * Fix the `json` check type. Reconcile possible sources of drift. Update now works as expected. * Normalize trigger durations to seconds. * Improve the robustness of the state handling for the `circonus_contact_group` resource. * I'm torn on this, but sort the contact groups in the notify list. This does mean that if the first contact group in the list has a higher lexical sort order the plan won't converge until the offending resource is tainted and recreated. But there's also some sorting happening elsewhere, so.... sort and taint for now and this will need to be revisited in the future. * Add support for the `httptrap` check type. * Remove empty units from the state file. * Metric clusters can return a 404. Detect this accordingly in its respective Exists handler. * Add a `circonus_graph` resource. * Fix a handful of bugs in the graph provider. * Re-enable the necessary `ConflictsWith` definitions and normalize attribute names. * Objects that have been deleted via the UI return a 404. Handle in Exists(). * Teach `circonus_graph`'s Stack set to accept nil values. * Set `ForceNew: true` for a graph's name. * Chase various API fixes required to make `circonus_graph` work as expected. * Fix up the handling of sub-1 zoom resolutions for graphs. * Add the `check_by_collector` out parameter to the `circonus_check` resource. * Improve validation of line vs area graphs. Fix graph_style. * Fix up the `logarithmic` graph axis option. * Resolve various trivial `go vet` issues. * Add a stream_group out parameter. * Remove incorrectly applied `Optional` attributes to the `circonus_account` resource. * Remove various `Optional` attributes from the `circonus_collector` data source. * Centralize the common need to suppress leading and trailing whitespace into `suppressWhitespace`. * Sync up with upstream vendor fixes for circonus_graph. * Update the checksum value for the http check. * Chase `circonus_graph`'s underlying `line_style` API object change from `string` to `string`. Clean up tests to use a generic terraform regression testing account. * Add support for the MySQL to the `circonus_check` resource. * Begin stubbing out the Circonus provider. * Remove all references to `reverse:secret_key`. This value is dynamically set by the service and unused by Terraform. * Update the `circonus_check` resource. Still a WIP. * Add docs for the `circonus_check` resource. Commit miss, this should have been included in the last commit. * "Fix" serializing check tags I still need to figure out how I can make them order agnostic w/o using a TypeSet. I'm worried that's what I'm going to have to do. * Spike a quick circonus_broker data source. * Convert tags to a Set so the order does not matter. * Add a `circonus_account` data source. * Correctly spell account. Pointed out by: @postwait * Add the `circonus_contact_group` resource. * Push descriptions into their own file in order to reduce the busyness of the schema when reviewing code. * Rename `circonus_broker` and `broker` to `circonus_collector` and `collector`, respectively. Change made with concent by Circonus to reduce confusion (@postwait, @maier, and several others). * Use upstream contsants where available. * Import the latest circonus-gometrics. * Move to using a Set of collectors vs a list attached to a single attribute. * Rename "cid" to "id" in the circonus_account data source and elsewhere where possible. * Inject a tag automatically. Update gometrics. * Checkpoint `circonus_metric` resource. * Enable provider-level auto-tagging. This is disabled by default. * Rearrange metric. This is an experimental "style" of a provider. We'll see. That moment. When you think you've gone off the rails on a mad scientist experiment but like the outcome and think you may be onto something but haven't proven it to yourself or anyone else yet? That. That exact feeling of semi-confidence while being alone in the wilderness. Please let this not be the Terraform provider equivalent of DJB's C style of coding. We'll know in another resource or two if this was a horrible mistake or not. * Begin moving `resource_circonus_check` over to the new world order/structure: Much of this is WIP and incomplete, but here is the new supported structure: ``` variable "used_metric_name" { default = "_usage`0`_used" } resource "circonus_check" "usage" { # collectors = ["${var.collectors}"] collector { id = "${var.collectors[0]}" } name = "${var.check_name}" notes = "${var.notes}" json { url = "https://${var.target}/account/current" http_headers = { "Accept" = "application/json" "X-Circonus-App-Name" = "TerraformCheck" "X-Circonus-Auth-Token" = "${var.api_token}" } } stream { name = "${circonus_metric.used.name}" tags = "${circonus_metric.used.tags}" type = "${circonus_metric.used.type}" } tags = { source = "circonus" } } resource "circonus_metric" "used" { name = "${var.used_metric_name}" tags = { source = "circonus" } type = "numeric" } ``` * Document the `circonus_metric` resource. * Updated `circonus_check` docs. * If a port was present, automatically set it in the Config. * Alpha sort the check parameters now that they've been renamed. * Fix a handful of panics as a result of the schema changing. * Move back to a `TypeSet` for tags. After a stint with `TypeMap`, move back to `TypeSet`. A set of strings seems to match the API the best. The `map` type was convenient because it reduced the amount of boilerplate, but you loose out on other things. For instance, tags come in the form of `category:value`, so naturally it seems like you could use a map, but you can't without severe loss of functionality because assigning two values to the same category is common. And you can't normalize map input or suppress the output correctly (this was eventually what broke the camel's back). I tried an experiment of normalizing the input to be `category:value` as the key in the map and a value of `""`, but... seee diff suppress. In this case, simple is good. While here bring some cleanups to _Metric since that was my initial testing target. * Rename `providerConfig` to `_ProviderConfig` * Checkpoint the `json` check type. * Fix a few residual issues re: missing descriptions. * Rename `validateRegexp` to `_ValidateRegexp` * Use tags as real sets, not just a slice of strings. * Move the DiffSuppressFunc for tags down to the Elem. * Fix up unit tests to chase the updated, default hasher function being used. * Remove `Computed` attribute from `TypeSet` objects. This fixes a pile of issues re: update that I was having. * Rename functions. `GetStringOk` -> `GetStringOK` `GetSetAsListOk` -> `GetSetAsListOK` `GetIntOk` -> `GetIntOK` * Various small cleanups and comments rolled into a single commit. * Add a `postgresql` check type for the `circonus_check` resource. * Rename various validator functions to be _CapitalCase vs capitalCase. * Err... finish the validator renames. * Add `GetFloat64()` support. * Add `icmp_ping` check type support. * Catch up to the _APIAttr renames. Deliberately left out of the previous commit in order to create a clean example of what is required to add a new check type to the `circonus_check` resource. Clarify when the `target` attribute is required for the `postgresql` check type. * Correctly pull the metric ID attribute from the right location. * Add a circonus_stream_group resource (a.k.a. a Circonus "metric cluster") * Add support for the [`caql`](https://login.circonus.com/user/docs/caql_reference) check type. * Add support for the `http` check type. * `s/SSL/TLS/g` * Add support for `tcp` check types. * Enumerate the available metrics that are supported for each check type. * Add [`cloudwatch`](https://login.circonus.com/user/docs/Data/CheckTypes/CloudWatch) check type support. * Add a `circonus_trigger` resource (a.k.a Circonus Ruleset). * Rename a handful of functions to make it clear in the function name the direction of flow for information moving through the provider. TL;DR: Replace `parse` and `read` with "foo to bar"-like names. * Fix the attribute name used in a validator. Absent != After. * Set the minimum `absent` predicate to 70s per testing. * Fix the regression tests for circonus_trigger now that absent has a 70s min * Fix up the `tcp` check to require a `host` attribute. Fix tests. It's clear I didn't run these before committing/pushing the `tcp` check last time. * Fix `circonus_check` for `cloudwatch` checks. * Rename `parsePerCheckTypeConfig()` to `_CheckConfigToAPI` to be consistent with other function names. grep(1)ability of code++ * Slack buttons as an integer are string encoded. * Fix updates for `circonus_contact`. * Fix the out parameters for contact groups. * Move to using `_CastSchemaToTF()` where appropriate. * Fix circonus_contact_group. Updates work as expected now. * Use `_StateSet()` in place of `d.Set()` everywhere. * Make a quick pass over the collector datasource to modernize its style * Quick pass for items identified by `golint`. * Fix up collectors * Fix the `json` check type. Reconcile possible sources of drift. Update now works as expected. * Normalize trigger durations to seconds. * Improve the robustness of the state handling for the `circonus_contact_group` resource. * I'm torn on this, but sort the contact groups in the notify list. This does mean that if the first contact group in the list has a higher lexical sort order the plan won't converge until the offending resource is tainted and recreated. But there's also some sorting happening elsewhere, so.... sort and taint for now and this will need to be revisited in the future. * Add support for the `httptrap` check type. * Remove empty units from the state file. * Metric clusters can return a 404. Detect this accordingly in its respective Exists handler. * Add a `circonus_graph` resource. * Fix a handful of bugs in the graph provider. * Re-enable the necessary `ConflictsWith` definitions and normalize attribute names. * Objects that have been deleted via the UI return a 404. Handle in Exists(). * Teach `circonus_graph`'s Stack set to accept nil values. * Set `ForceNew: true` for a graph's name. * Chase various API fixes required to make `circonus_graph` work as expected. * Fix up the handling of sub-1 zoom resolutions for graphs. * Add the `check_by_collector` out parameter to the `circonus_check` resource. * Improve validation of line vs area graphs. Fix graph_style. * Fix up the `logarithmic` graph axis option. * Resolve various trivial `go vet` issues. * Add a stream_group out parameter. * Remove incorrectly applied `Optional` attributes to the `circonus_account` resource. * Remove various `Optional` attributes from the `circonus_collector` data source. * Centralize the common need to suppress leading and trailing whitespace into `suppressWhitespace`. * Sync up with upstream vendor fixes for circonus_graph. * Update the checksum value for the http check. * Chase `circonus_graph`'s underlying `line_style` API object change from `string` to `string`. Clean up tests to use a generic terraform regression testing account. * Rename all identifiers that began with a `_` and replace with a corresponding lowercase glyph. * Remove stale comment in types. * Move the calls to `ResourceData`'s `SetId()` calls to be first in the list so that no resources are lost in the event of a `panic()`. * Remove `stateSet` from the `circonus_trigger` resource. * Remove `stateSet` from the `circonus_stream_group` resource. * Remove `schemaSet` from the `circonus_graph` resource. * Remove `stateSet` from the `circonus_contact` resource. * Remove `stateSet` from the `circonus_metric` resource. * Remove `stateSet` from the `circonus_account` data source. * Remove `stateSet` from the `circonus_collector` data source. * Remove stray `stateSet` call from the `circonus_contact` resource. This is an odd artifact to find... I'm completely unsure as to why it was there to begin with but am mostly certain it's a bug and needs to be removed. * Remove `stateSet` from the `circonus_check` resource. * Remove the `stateSet` helper function. All call sites have been converted to return errors vs `panic()`'ing at runtime. * Remove a pile of unused functions and type definitions. * Remove the last of the `attrReader` interface. * Remove an unused `Sprintf` call. * Update `circonus-gometrics` and remove unused files. * Document what `convertToHelperSchema()` does. Rename `castSchemaToTF` to `convertToHelperSchema`. Change the function parameter ordering so the `map` of attribute descriptions: this is much easier to maintain when the description map is first when creating schema inline. * Move descriptions into their respective source files. * Remove all instances of `panic()`. In the case of software bugs, log an error. Never `panic()` and always return a value. * Rename `stream_group` to `metric_cluster`. * Rename triggers to rule sets * Rename `stream` to `metric`. * Chase the `stream` -> `metric` change into the docs. * Remove some unused test functions. * Add the now required `color` attribute for graphing a `metric_cluster`. * Add a missing description to silence a warning. * Add `id` as a selector for the account data source. * Futureproof testing: Randomize all asset names to prevent any possible resource conflicts. This isn't a necessary change for our current build and regression testing, but just in case we have a radical change to our testing framework in the future, make all resource names fully random. * Rename various values to match the Circonus docs. * s/alarm/alert/g * Ensure ruleset criteria can not be empty.	9 years ago
Paul Stack	79736577ba	provider/aws: Bump SDK to 1.7.7 (#12591 ) Required for ACM and API Gateway integration	9 years ago
Andy Lindeman	fa18174713	Updates heroku-go to the latest revision (#12575 )	9 years ago
Joe Topjian	2a136ef09b	vendor: Updating Gophercloud for OpenStack (#12577 )	9 years ago
Alexander	8482dda375	Vendor update (#12559 )	9 years ago
Paul Stack	0491638343	provider/aws: Bump SDK to 1.7.5 (#12535 )	9 years ago
Joe Topjian	3759e36784	provider/cobbler: Profile and System Fixes (#12452 ) * vendor: Updating cobblerclient for Cobbler * provider/cobbler: Fix Profile Repos This commit fixes a bug where adding repos would result in an error. This was due to the Cobbler API wanting a space-separated list of repos rather than an array. The Cobbler Service will split the string by space when used internally, but will always present the repos as a string. * provider/cobbler: System Interface Management Test This commit adds a test to verify that the Management parameter of System Interfaces works.	9 years ago
Paul Stack	d10ec314bf	provider/aws: Bump AWS SDK to 1.7.3 (#12325 ) This allows the creation of Organisations	9 years ago
Peter McAtominey	d42890ca95	provider/azurerm: update SDK to v8.1.0-beta (#12362 )	9 years ago
Simone Carletti	8ae31740e3	Upgrade DNSimple provider to API v2 (#10760 ) * Replace DNSimple API client with the official Go client * Upgrade DNSimple provider to use the new API v2 Acceptance tests pass: ``` === RUN TestProvider --- PASS: TestProvider (0.00s) === RUN TestProvider_impl --- PASS: TestProvider_impl (0.00s) === RUN TestAccDNSimpleRecord_Basic --- PASS: TestAccDNSimpleRecord_Basic (2.67s) === RUN TestAccDNSimpleRecord_Updated --- PASS: TestAccDNSimpleRecord_Updated (1.88s) PASS ok github.com/hashicorp/terraform/builtin/providers/dnsimple ``` Note that the code still has to be updated to pass the account ID dynamically in place of "TODO-ACCOUNT". * Refactor DNSimple provider to expose both client and config The config is required as the new API wants to know the identifier of the account you are operating to. The account is not stored in the client (as the client can talk with different accounts), hence I need to pass it as part of the config. * Identify Terraform requests to DNSimple via UserAgent * Upgrade to the latest dnsimple-go version * Update docs Provide upgrade instructions and update the docs for API v2. * Remove rendundant type declaration	9 years ago
Alexander	59d1d7056c	provider/pagerduty: Updated implementation of pagerduty_vendor & pagerduty_service_integration (#12357 ) * Vendor update * Updated implementation of pagerduty_vendor * Update pagerduty_vendor tests * Update pagerduty_vendor documentation * Updated implementation of pagerduty_service_integration * Update pagerduty_service_integration tests * Update pagerduty_service_integration documentation	9 years ago
Radek Simko	914e86d087	vendor: k8s.io/kubernetes/pkg/api/validation@v1.5.3 (#12267 )	9 years ago
James Bardin	79e13b92d9	remove the docker packages that aren't needed govendor pulled these in, not sure why.	9 years ago
James Bardin	0220b83466	remove scaleway-cli package with borken deps github.com/scaleway/scaleway-cli/pkg/utils can be imported because it depends on github.com/moul/gotty-client which can't build on solaris. This requires removing the github.com/scaleway/scaleway-cli/pkg/api/helpers.go file which imports the utils package, and we don't use. Not sure how we'll handle this if the structure of the scaleway package changes and we can't break this import any longer.	9 years ago
James Bardin	065e159464	remove gotty-client ... again this is still broken on solaris	9 years ago
James Bardin	359170d5d7	sync scaleway packages multiple scaleway-cli packages were out of sync, unfortunately this pulled in some other updates.	9 years ago
James Bardin	6fd891f5e2	Make sure all azure-sdk packages match The containerservice package fell behind the others. Fix the vendor.json file to match the vendored packages.	9 years ago
Radek Simko	8ce8839397	vendor: k8s.io/kubernetes/pkg/...@v1.5.3 (#12230 )	9 years ago
Paul Stack	05e87be7d5	provider/azurerm: Bump AzureRM SDK to v8.0.1-beta (#11866 ) * provider/azurerm: Bump AzureRM SDK to v8.0.1-beta * provider/azurerm: Renaming SDK packages as per MSFT updates * Bump azurerm sdk 8.0.1 (#12076) * Updating the constructors to match the updated types * Updating the Redis Client name * ObjectID is now a string * Updating to match the new Storage API specs	9 years ago
Liran Polak	f37800ae62	New Provider: Spotinst (#5001 ) * providers/spotinst: Add support for Spotinst resources * providers/spotinst: Fix merge conflict - layouts/docs.erb * docs/providers/spotinst: Fix the resource description field * providers/spotinst: Fix the acceptance tests * providers/spotinst: Mark the device_index as a required field * providers/spotinst: Change the associate_public_ip_address field to TypeBool * docs/providers/spotinst: Update the description of the adjustment field * providers/spotinst: Rename IamRole to IamInstanceProfile to make it more compatible with the AWS provider * docs/providers/spotinst: Rename iam_role to iam_instance_profile * providers/spotinst: Deprecate the iam_role attribute * providers/spotinst: Fix a misspelled var (IamRole) * providers/spotinst: Fix possible null pointer exception related to "iam_instance_profile" * docs/providers/spotinst: Add "load_balancer_names" missing description * providers/spotinst: New resource "spotinst_subscription" added * providers/spotinst: Eliminate a possible null pointer exception in "spotinst_aws_group" * providers/spotinst: Eliminate a possible null pointer exception in "spotinst_subscription" * providers/spotinst: Mark spotinst_subscription as deleted in destroy * providers/spotinst: Add support for custom event format in spotinst_subscription * providers/spotinst: Disable the destroy step of spotinst_subscription * providers/spotinst: Add support for update subscriptions * providers/spotinst: Merge fixed conflict - layouts/docs.erb * providers/spotinst: Vendor dependencies * providers/spotinst: Return a detailed error message * provider/spotinst: Update the plugin list * providers/spotinst: Vendor dependencies using govendor * providers/spotinst: New resource "spotinst_healthcheck" added * providers/spotinst: Update the Spotinst SDK * providers/spotinst: Comment out unnecessary log.Printf * providers/spotinst: Fix the acceptance tests * providers/spotinst: Gofmt fixes * providers/spotinst: Use multiple functions to expand each block * providers/spotinst: Allow ondemand_count to be zero * providers/spotinst: Change security_group_ids from TypeSet to TypeList * providers/spotinst: Remove unnecessary `ForceNew` fields * providers/spotinst: Update the Spotinst SDK * providers/spotinst: Add support for capacity unit * providers/spotinst: Add support for EBS volume pool * providers/spotinst: Delete health check * providers/spotinst: Allow to set multiple availability zones * providers/spotinst: Gofmt * providers/spotinst: Omit empty strings from the load_balancer_names field * providers/spotinst: Update the Spotinst SDK to v1.1.9 * providers/spotinst: Add support for new strategy parameters * providers/spotinst: Update the Spotinst SDK to v1.2.0 * providers/spotinst: Add support for Kubernetes integration * providers/spotinst: Fix merge conflict - vendor/vendor.json * providers/spotinst: Update the Spotinst SDK to v1.2.1 * providers/spotinst: Add support for Application Load Balancers * providers/spotinst: Do not allow to set ondemand_count to 0 * providers/spotinst: Update the Spotinst SDK to v1.2.2 * providers/spotinst: Add support for scaling policy operators * providers/spotinst: Add dimensions to spotinst_aws_group tests * providers/spotinst: Allow both ARN and name for IAM instance profiles * providers/spotinst: Allow ondemand_count=0 * providers/spotinst: Split out the set funcs into flatten style funcs * providers/spotinst: Update the Spotinst SDK to v1.2.3 * providers/spotinst: Add support for EBS optimized flag * providers/spotinst: Update the Spotinst SDK to v2.0.0 * providers/spotinst: Use stringutil.Stringify for debugging * providers/spotinst: Update the Spotinst SDK to v2.0.1 * providers/spotinst: Key pair is now optional * providers/spotinst: Make sure we do not nullify signals on strategy update * providers/spotinst: Hash both Strategy and EBS Block Device * providers/spotinst: Hash AWS load balancer * providers/spotinst: Update the Spotinst SDK to v2.0.2 * providers/spotinst: Verify namespace exists before appending policy * providers/spotinst: Image ID will be in a separate block from now on, so as to allow ignoring changes only on the image ID. This change is backwards compatible. * providers/spotinst: user data decoded when returned from spotinst api, so that TF compares the two states properly, and does not update without cause.	9 years ago
Erik Jansson	62aa2c583a	provider/aws: New resource codepipeline (#11814 ) * provider/aws: New resource codepipeline * Vendor aws/codepipeline * Add tests * Add docs * Bump codepipeline to v1.6.25 * Adjustments based on feedback * Force new resource on ID change * Improve tests * Switch update to read Since we don't require a second pass, only do a read. * Skip tests if GITHUB_TOKEN is not set	9 years ago
Paul Stack	8e41f57694	provider/aws: Bump SDK to 1.6.25 (#12084 )	9 years ago
Joe Topjian	8ea8588c52	provider/openstack: Image Data Source (#12097 ) * vendor: Updating Gophercloud * provider/openstack: Image Data Source This commit adds the openstack_images_image_v2 data source which is able to query the Image Service v2 API for a specific image.	9 years ago
Otto Jongerius	2310316666	provider/datadog: Upgrade to Datadog API v2 (#12098 ) * provider/datadog: Pulls v2 and removes v1 of library go-datadog-api. See https://github.com/zorkian/go-datadog-api/issues/56 for context. * Fixes bug in backoff implementation that decreased performance significantly. * Uses pointers for field types, providing support of distinguishing between if a value is set, or the default value for that type is effective. * provider/datadog: Convert provider to use v2 of go-datadog-api. * provider/datadog: Update vendored library. * provider/datadog: Update dashboard resource to reflect API updates.	9 years ago
Joe Topjian	b3b9247ad0	Merge pull request #11942 from yanndegat/master Add resource_openstack_images_image_v2	9 years ago
clint shryock	be6ae20ac1	Merge branch 'pr-8299' * pr-8299: Patch up website docs provider/dns: DNS dynamic updates (RFC 2136) vendor: Capture new dependency miekg-dns	9 years ago
Mitchell Hashimoto	3c543a4d6f	vendor: update HCL (formatting)	9 years ago
Mitchell Hashimoto	8ee3be9d55	Merge pull request #12048 from hashicorp/b-update-go-pllugin vendor: update go-plugin	9 years ago
Mitchell Hashimoto	6cc5123d31	vendor: update go-plugin This fixes some hanging issues seen by TF users, see the relevant commits in go-plugin.	9 years ago
Jesse Szwedko	5b7e3701cb	[datadog] add support for new host delay to the datadog_monitor resource (#11975 ) * [datadog] Update go-datadog-api library Involves one breaking API change. Also some `gofmt`ing. * [datadog] Add support for new_host_delay to the datadog_monitor resource New API parameter that Datadog added for monitors to ignore new hosts for the specified time period in monitor evaluation.	9 years ago
Sean Chittenden	7063ee1af2	Update `github.com/hashicorp/consul/api` to the latest and greatest.	9 years ago
Yann DEGAT	02eda6f0c9	vendor: Updating Gophercloud	10 years ago
Paul Stack	ad69c540b8	provider/statuscake: Bump Statuscake SDK version (#11985 )	10 years ago
Paul Stack	cae76db1ba	provider/aws: Bump SDK version fo 1.6.22 (#11968 ) Adds support for EBS Elastic Volumes	10 years ago
Paul Stack	f681fbf4f6	provider/digitalocean: Bump SDK version of godo for loadbalancer support (#11964 )	10 years ago
Joe Topjian	47bf2eff09	provider/openstack BlockStorage v1 availability_zone Fix (#11949 ) * vendor: Updating Gophercloud * provider/openstack: Fix upstream AvailabilityZone field This commit complements an upstream fix where "availability" was being sent instead of "availability_zone".	10 years ago
Mitchell Hashimoto	488d5f41e6	vendor: add shellwords	10 years ago
Kazumichi Yamamoto	cd7f69ab11	New provider arukas (#11171 ) * Add a Arukas provider * Add dependencies for the Arukas provider * Add documents for the Arukas	10 years ago
Jake Champlin	804c1cdef7	core: Update go-cleanhttp vendored dependency Updates go-cleanhttp vendored dependency	10 years ago
Tom Harvey	f349309a8f	provider/azurerm: Container Service (#10820 ) * Importing v7.0.1 of the SDK * Configuring the Container Service Client * Scaffolding the Container Service resource * Scaffolding the Website documentation * Completing the documentation * Acceptance Tests for Kubernetes Azure Container Service * DCOS / Swarm tests * Parsing values back from the API properly * Fixing the test * Service Principal can be optional. Because of course it can. * Validation for the Container Service Count's * Updating the docs * Updating the field required values * Making the documentation more explicit * Fixing the build * Examples for DCOS and Swarm * Removing storage_uri for now * Making the SSH Key required as per the docs * Resolving the merge conflicts * Removing the unused error's * Adding Hash's to the schema's * Switching out the provider registration * Fixing the hash definitions * Updating keydata to match * Client Secret is sensitive * List -> Set * Using the first item for the diagnostic_profile * Helps if you actually update the type * Updating the docs to include the Computed fields * Fixing comments / removing redundant optional checks * Removing the FQDN's from the examples * Moving the Container resources together	10 years ago
Roberto Jung Drebes	04b698f409	vendor: Capture new dependency miekg-dns	10 years ago
Gauthier Wallet	045bb1039f	Bumped AWS SDK to 1.6.20 (#11846 )	10 years ago
Paul Stack	bfbd5ad4e6	provider/aws: Bump SDK version to 1.6.19 (#11775 )	10 years ago
Mitchell Hashimoto	34227e5a9c	vendor: update go-getter for #11438	10 years ago
Mitchell Hashimoto	244992c1be	vendor: update HCL	10 years ago
Jake Champlin	5481fd941a	provider/fastly: Allow specifying log format version Allows the user to specify the log format version when setting up `s3logging` on the fastly service resource. Requires an update to the vendored `go-fastly` dependency. Also adds an additional acceptance test for the new attribute. ``` $ make testacc TEST=./builtin/providers/fastly TESTARGS='-run=TestAccFastlyServiceV1_s3logging' ==> Checking that code complies with gofmt requirements... go generate $(go list ./... \| grep -v /terraform/vendor/) 2017/02/06 14:51:55 Generated command/internal_plugin_list.go TF_ACC=1 go test ./builtin/providers/fastly -v -run=TestAccFastlyServiceV1_s3logging -timeout 120m === RUN TestAccFastlyServiceV1_s3logging_basic --- PASS: TestAccFastlyServiceV1_s3logging_basic (36.11s) === RUN TestAccFastlyServiceV1_s3logging_s3_env --- PASS: TestAccFastlyServiceV1_s3logging_s3_env (15.35s) === RUN TestAccFastlyServiceV1_s3logging_formatVersion --- PASS: TestAccFastlyServiceV1_s3logging_formatVersion (15.71s) PASS ok github.com/hashicorp/terraform/builtin/providers/fastly 67.186s ```	10 years ago
Jake Champlin	9532c84f76	structs package now includes entire helper package	10 years ago
Jake Champlin	79c117877e	provider/nomad: Update jobspec parser Updates vendored Nomad jobspec parser such that parameterized nomad job files can no be parsed and used with Terraform. Also fixes tests to adhere to new jobspec version, and update documentation to reflect such as well.	10 years ago

1 2 3 4 5 ...

413 Commits (cdc3fa8337bd7a0be06bbd2fe2aee2fdbd17e4ec)