inspec/test/fixtures/profiles/waivers/namespace-clash/inspec.yml

name: namespace-clash
summary: Verifies input and control namespace can safely clash
version: 0.1.0
supports:
  platform: os
Allows input and control to have the same name In https://github.com/inspec/inspec/issues/4936 the issue was reported that naming an input the same as a control caused an unexpected failure. In that particular case, the naming was a result of a pre-waivers workaround which is no longer necessary, but ultimately a breakage of that name clash is an unexpected occurrance. Due to how inputs are named and registered, `__apply_waivers` thinks that an object is a waiver that is not a waiver and tries to process it. On the micro level, it breaks when trying to pass a variable to a string as if it were a Hash. It is imperative that we preserve 100% of the current featureset, pass our tests, and fix this edge case along with new test coverage for the failure. This PR updates the code to do a slightly more elegant and small ‘waiver check’ to stop the namespace clash from breaking our code. Signed-off-by: Nick Schwaderer <nschwaderer@chef.io> 2020-04-29 10:52:28 +00:00			`name: namespace-clash`
			`summary: Verifies input and control namespace can safely clash`
			`version: 0.1.0`
			`supports:`
			`platform: os`