Chris Marchesi d41b806789 core: Restore CountBoundaryTransformer to apply, add/adjust tests ... Moving the transformer wholesale looks like it broke some tests, with some actually doing legit work in normalizing singular resources from a foo.0 notation to just foo. Adjusted the TestPlanGraphBuilder to account for the extra meta.count-boundary nodes in the graph output now, as well as added another context test that tests this case. It appears the issue happens during validate, as this is where the state can be altered to a broken state if things are not properly transformed in the plan graph.		2017-04-19 22:23:52 -07:00
..
data_source.go	provider/test: Add test of data source count.index	2016-09-03 13:58:30 -07:00
data_source_test.go	core: Restore CountBoundaryTransformer to apply, add/adjust tests	2017-04-19 22:23:52 -07:00
provider.go	flatmap: mark computed list as a computed value in Expand	2017-02-23 10:03:59 -08:00
provider_test.go	core: Fix issues with ignore_changes	2016-03-21 14:20:36 -05:00
resource.go	provider/test: Add test of data source count.index	2016-09-03 13:58:30 -07:00
resource_gh12183.go	flatmap: mark computed list as a computed value in Expand	2017-02-23 10:03:59 -08:00
resource_gh12183_test.go	flatmap: mark computed list as a computed value in Expand	2017-02-23 10:03:59 -08:00
resource_test.go	Add a provider test for a list of maps	2016-12-16 10:36:26 -05:00