14 Commits (2bd3c26fb11bd3d51cdf364c78f36ba767956475)

Author	SHA1	Message	Date
James Bardin	fc13a1b814	Disaply interpolation strings for computed fields ... Displaying interpolations strings when possible for computed fields in the plan output makes for a nicer UX	9 years ago
Mitchell Hashimoto	8701434b4d	command: plan formatting for deposed destroy	9 years ago
James Bardin	db83a779ab	Fix plan output for data sources ... Data sources are given a special plan output when the diff would show it creating a new resource, to indicate that there is only a logical data resource being read. Data sources nested in modules weren't formatted in the plan output in the same way. This checks for the "data." part of the path in nested modules, and adds acceptance tests for the plan output.	10 years ago
Chris Marchesi	9d7fb89114	core: Adding Sensitive attribute to resource schema ... This an effort to address hashicorp/terraform#516. Adding the Sensitive attribute to the resource schema, opening up the ability for resource maintainers to mark some fields as sensitive. Sensitive fields are hidden in the output, and, possibly in the future, could be encrypted.	10 years ago
Sander van Harmelen	8560f50cbc	Change taint behaviour to act as a normal resource ... This means it’s shown correctly in a plan and takes into account any actions that are dependant on the tainted resource and, vice verse, any actions that the tainted resource depends on. So this changes the behaviour from saying this resource is tainted so just forget about it and make sure it gets deleted in the background, to saying I want that resource to be recreated (taking into account the existing resource and it’s place in the graph).	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
Sharif Nassar	2e51915431	Colorize the 'forces new resource' message. ... Sometimes in all the output from ```terraform plan```, it is difficult to see the ```(forces new resource)``` message. This patch adds a little bit of color.	11 years ago
Mitchell Hashimoto	8c17062638	command: plan shows module-level, can control depth	12 years ago
Mitchell Hashimoto	672bf58337	command: compiles, tests don't pass yet	12 years ago
Mitchell Hashimoto	2094326c10	command: plan that requires destroy and new is "-/+"	12 years ago
Mitchell Hashimoto	dbc1c63d79	command/show	12 years ago
Mitchell Hashimoto	c615afc097	command/apply: improved output, still not done	12 years ago
Mitchell Hashimoto	832211c17a	command/plan: nice plan formatting	12 years ago