Chris Marchesi eef933f2a7 core: Don't count scaled-out resources twice in the UI ... This fixes a bug with the new refresh graph behaviour where a resource was being counted twice in the UI on part of being scaled out: * We are no longer transforming refresh nodes without state to plannable resources (the transformer will be removed shortly) * A Quiet flag has been added to EvalDiff and InstanceDiff - this allows for the flagging of a diff that should not be treated as real diff for purposes of planning * When there is no state for a refresh node now, a new path is taken that is similar to plan, but flags Quiet, and does nothing with the diff afterwards. Tests pending - light testing has confirmed this should fix the double count issue, but we should have some tests to actually confirm the bug.		2017-06-20 07:37:32 -07:00
..
atlas	backend/atlas: accept ATLAS_ADDRESS env var for address	2017-03-16 23:04:07 -07:00
init	convert S3 remote state to a backend	2017-03-22 10:59:37 -04:00
legacy	Make backcend/legacy match new Backend iface	2017-02-28 16:35:45 -05:00
local	core: Don't count scaled-out resources twice in the UI	2017-06-20 07:37:32 -07:00
remote-state	rename aws provider import in s3 backend	2017-06-12 13:43:51 -04:00
backend.go	backend: Operation.Environment renamed to "Workspace"	2017-06-09 16:26:26 -07:00
cli.go	command: use backend.CLIIinit	2017-02-28 10:58:29 -08:00
nil_test.go	backend: introduce the backend set of interfaces	2017-01-26 14:33:49 -08:00
nil.go	Update Backend interface to latest iteration	2017-02-28 16:07:07 -05:00
operation_type.go	backend: introduce the backend set of interfaces	2017-01-26 14:33:49 -08:00
operationtype_string.go	Fix stringer comments (#15069)	2017-06-05 10:17:35 +01:00
testing.go	test for proper state persistence	2017-03-23 10:06:07 -04:00