10436 Commits (6a08e893e37ee2ca1dde05d36bbee5d8edca790d)

 

All Branches   

Search

Author	SHA1	Message	Date
Sander van Harmelen	6a08e893e3	Use the new option to list ACLs based on the ID and VPC ID	10 years ago
Sander van Harmelen	640152e310	Update `go-cloudstack` dependency	10 years ago
thetuxkeeper	62639620e1	merged createVirtualMachine and deployVirtualMachine to setupVirtualMachine (#6659)	10 years ago
Clint	40db82f25e	Update CHANGELOG.md	10 years ago
Clint	073f629447	provider/fastly: add support for custom VCL configuration (supersedes #6587) (#6662) ... * provider/fastly: add support for custom VCL configuration	10 years ago
James Nugent	3edbb36b9d	Merge pull request #6719 from glasser/patch-1 ... docs: clarify an internal-plugins header	10 years ago
James Nugent	e496e561b3	Remove CHANGELOG entry for backported 0.6.17 feature	10 years ago
Joe Topjian	d3b0a301c7	Merge pull request #6718 from buzztroll/vet/keyed_fields ... provider/openstack: Fixes an vet error.	10 years ago
Paul Stack	71def12259	Update CHANGELOG.md	10 years ago
thetuxkeeper	790115fe43	provider/vsphere: wait for network enhanced (#6377) ... * - use WaitForNetIP - removed duplicate wait for network parts * gofmt fix * fixes	10 years ago
James Nugent	6139b43c95	Update CHANGELOG.md	10 years ago
James Nugent	3b6cd9918a	Merge pull request #6622 from hashicorp/f-fastly-request-settings ... provider/fastly: Add support for Service Request Settings	10 years ago
James Nugent	95ceb51aef	Update CHANGELOG.md	10 years ago
James Nugent	55002086e5	Merge pull request #6592 from hashicorp/b-aws-r53-name-state ... provider/aws: Update Route53 Record to schema v1, normalizing name	10 years ago
James Nugent	1d837b4c76	Update CHANGELOG.md	10 years ago
James Nugent	b08d741eb0	Merge pull request #6687 from hashicorp/b-aws-elasticache-param-crash ... provider/aws: Fix crash in ElastiCache param group	10 years ago
David Glasser	c3cc0b2538	docs: clarify an internal-plugins header	10 years ago
John Bresnahan	99ab233740	Fixes an vet error.	10 years ago
Clint	592162c92a	Update CHANGELOG.md	10 years ago
Robert Conrad	faa6ddb2ee	provider/aws: Support for Redshift Cluster encryption using a KMS key (#6712)	10 years ago
clint shryock	91a1097041	provider/aws: Randomize key names in KMS alias test	10 years ago
jkburges	ef3de51199	Include the list of allowed values for AWS auto scaling group termination policies (#6710) ... Ref: http://docs.aws.amazon.com/autoscaling/latest/userguide/as-instance-termination.html#custom-termination-policy	10 years ago
James Nugent	cb8054137b	Merge pull request #6703 from igable/azurerm-custom-image-docs ... website: docs for azurerm custom images	10 years ago
James Nugent	adf3dcb482	Merge pull request #6696 from josephholsten/rm-dup-columnize ... Godeps: rm dup github.com/ryanuber/columnize	10 years ago
Ian Gable	988c8144c0	website: docs for azurerm custom images ... Adds docs on booting custom images with the azurerm_virtual_machine resource; this was previously undocumented.	10 years ago
James Nugent	1bb3c7d016	Merge pull request #6694 from hashicorp/sethvargo/training ... Add note about paid training	10 years ago
James Nugent	6401344234	Update CHANGELOG.md	10 years ago
Joseph Anthony Pasquale Holsten	e9915d2112	Godeps: rm dup github.com/ryanuber/columnize	10 years ago
Seth Vargo	0088b33b84	Add note about paid training	10 years ago
James Nugent	a2950c76d9	Merge pull request #6598 from hashicorp/f-data-sources ... Data-driven Terraform Configuration	10 years ago
clint shryock	23340d3c84	provider/aws: Fix crash in ElastiCache param group	10 years ago
clint shryock	b9d0e14d2a	provider/aws: Update Lambda tests for more random names	10 years ago
Aki Hänninen	fce7aa483d	Add version_id attribute for aws_s3_bucket_object (#6677)	10 years ago
James Nugent	ffcf6cf6f7	Merge pull request #6675 from atward/build_check ... Don't assume dev platform was built	10 years ago
Adam Ward	4a29be7b50	Don't assume dev platform was built	10 years ago
Joe Topjian	76e1a8ffb4	Update CHANGELOG.md	10 years ago
Joe Topjian	f69d95d01f	Merge pull request #6579 from Fodoj/reassociate-fip-on-update ... provider/openstack: Reassociate FIP on network changes	10 years ago
Joe Topjian	94d27ba3ea	Update CHANGELOG.md	10 years ago
Joe Topjian	b53c74a9ae	Merge pull request #6279 from ZZelle/support-client-cert ... provider/openstack: Support client certificates	10 years ago
Martin Atkins	453fc505f4	core: Tolerate missing resource variables during input walk ... Provider nodes interpolate their config during the input walk, but this is very early and so it's pretty likely that any resources referenced are entirely absent from the state. As a special case then, we tolerate the normally-fatal case of having an entirely missing resource variable so that the input walk can complete, albeit skipping the providers that have such interpolations. If these interpolations end up still being unresolved during refresh (e.g. because the config references a resource that hasn't been created yet) then we will catch that error on the refresh pass, or indeed on the plan pass if -refresh=false is used.	10 years ago
Martin Atkins	f95dccf1b3	provider/null: null_data_source data source ... A companion to the null_resource resource, this is here primarily to enable manual quick testing of data sources workflows without depending on any external services. The "inputs" map gets copied to the computed "outputs" map on read, "rand" gives a random number to exercise cases with constantly-changing values (an anti-pattern!), and "has_computed_default" is settable in config but computed if not set.	10 years ago
Martin Atkins	2ca10ad962	command: Show data source reads differently in plans ... Internally a data source read is represented as a creation diff for the resource, but in the UI we'll show it as a distinct icon and color so that the user can more easily understand that these operations won't affect any real infrastructure. Unfortunately by the time we get to formatting the plan in the UI we only have the resource names to work with, and can't get at the original resource mode. Thus we're forced to infer the resource mode by exploiting knowledge of the naming scheme.	10 years ago
Martin Atkins	bfee4b0295	command: don't show old values for create diffs in plan ... New resources logically don't have "old values" for their attributes, so showing them as updates from the empty string is misleading and confusing. Instead, we'll skip showing the old value in a creation diff.	10 years ago
Martin Atkins	5d27a5b3e2	command: Show id only when refreshing managed resources ... Data resources don't have ids when they refresh, so we'll skip showing the "(ID: ...)" indicator for these. Showing it with no id makes it look like something is broken.	10 years ago
Martin Atkins	60c24e3319	command: Prevent data resources from being tainted ... Since the data resource lifecycle contains no steps to deal with tainted instances, we must make sure that they never get created. Doing this out in the command layer is not the best, but this is currently the only layer that has enough information to make this decision and so this simple solution was preferred over a more disruptive refactoring, under the assumption that this taint functionality eventually gets reworked in terms of StateFilter anyway.	10 years ago
Martin Atkins	61ab8bf39a	core: ResourceAddress supports data resources ... The ResourceAddress struct grows a new "Mode" field to match with Resource, and its parser learns to recognize the "data." prefix so it can set that field. Allows -target to be applied to data sources, although that is arguably not a very useful thing to do. Other future uses of resource addressing, like the state plumbing commands, may be better uses of this.	10 years ago
Martin Atkins	afc7ec5ac0	core: Destroy data resources with "terraform destroy" ... Previously they would get left behind in the state because we had no support for planning their destruction. Now we'll create a "destroy" plan and act on it by just producing an empty state on apply, thus ensuring that the data resources don't get left behind in the state after everything else is gone.	10 years ago
Martin Atkins	4d50f22a23	core: separate lifecycle for data resource "orphans" ... The handling of data "orphans" is simpler than for managed resources because the only thing we need to deal with is our own state, and the validation pass guarantees that by the time we get to refresh or apply the instance state is no longer needed by any other resources and so we can safely drop it with no fanfare.	10 years ago
Martin Atkins	36054470e4	core: lifecycle for data resources ... This implements the main behavior of data resources, including both the early read in cases where the configuration is non-computed and the split plan/apply read for cases where full configuration can't be known until apply time.	10 years ago
Martin Atkins	1da560b653	core: Separate resource lifecycle for data vs. managed resources ... The key difference between data and managed resources is in their respective lifecycles. Now the expanded resource EvalTree switches on the resource mode, generating a different lifecycle for each mode. For this initial change only managed resources are implemented, using the same implementation as before; data resources are no-ops. The data resource implementation will follow in a subsequent change.	10 years ago