19 Commits (da74b59ea1d3aa4d7706579c95f63c778f2e515e)

Author	SHA1	Message	Date
Radek Simko	0fe906fa8c	make copyrightfix	2 months ago
Daniel Schmidt	84eeb0a113	improve wording of comments	3 months ago
Daniel Schmidt	edfe22d479	match naming scheme	3 months ago
Daniel Schmidt	69adc6a4c7	remove dead code	3 months ago
Daniel Schmidt	9cf9235582	track down precise deprecation locations in complex output values	3 months ago
Daniel Schmidt	5ed7d5134e	refactor deprecation diag creation	3 months ago
Daniel Schmidt	3fd7a5052f	limit the amount of additional remove deprecation mark calls	3 months ago
Daniel Schmidt	11e49b983a	only unmark deep once for Validate	3 months ago
Daniel Schmidt	c7bc22ed79	only unmark deep once for ValidateDeep	3 months ago
Daniel Schmidt	76747e174c	use format.CtyPath for formatting go-cty paths	3 months ago
Daniel Schmidt	7b28c88e66	improve wording of deprecation marks	3 months ago
Daniel Schmidt	7eaf6daf60	add deprecation marks to resources based on schema	3 months ago
Daniel Schmidt	379fa79c3e	ElaborateFromConfigBody handles deeply nested paths more precisely	3 months ago
Daniel Schmidt	b09ef138fc	use validate for primitive types	3 months ago
Daniel Schmidt	e6d969a2eb	we only want to send diagnostics for deeply nested deprecations in certain locations ... Mainly terminal locations for the value where they are used, such as the config of a resource, for_each, outputs. We don't want to evaluate the deprecation deeply when it comes to values where the value is not yet used, e.g. locals This is because if e.g. a deeply nested value is deprecated it should still be ok for the entire object to be in a local whereas the same object should give a warning in e.g. an output	3 months ago
Daniel Schmidt	2f392d904e	deprecation.Validate should only check top-level marks	3 months ago
Daniel Schmidt	75445e1ef8	use a string as deprecation origin to help with indirect references ... We want to be able to give better information if e.g. the entire module is stored in a local and the deprecated value is only later used. Where the diag is emitted we might only see the local and not the true origin of the deprecation A string identifying the source of the deprecation should help	3 months ago
Daniel Schmidt	ea7f1e3043	add extra origin information for deprecation diagnostics	3 months ago
Daniel Schmidt	13247d19e2	add deprecation singleton ... This struct tracks and validates deprecations in the context of a graph walk. We need a struct to keep track of the module calls that opt-out of deprecation warnings.	3 months ago