(PUP-12077) Use stringify_rich instead of rich_data in resource application

Author: justinstoller

lib/puppet/application/resource.rb

@@ -155,7 +155,7 @@ def main
 
       if options[:to_yaml]
         data = resources.map do |resource|
-          Puppet.override(rich_data: false) do
+          Puppet.override(stringify_rich: true) do
             resource.prune_parameters(:parameters_to_include => @extra_params).to_hiera_hash
           end
         end.inject(:merge!)

spec/unit/application/resource_spec.rb

@@ -170,15 +170,6 @@ def string
       expect { @resource_app.main }.not_to raise_error
     end
 
-    it "should raise an error when printing yaml if rich_data is off" do
-      @resource_app.options[:to_yaml] = true
-      allow(@resource_app.command_line).to receive(:args).and_return(['stringify', 'hello', 'ensure=present', 'string=asd'])
-      Puppet.override(rich_data: false) do
-        expect { @resource_app.main }.to raise_error( Puppet::PreformattedError,
-          /Stringify\[hello\]\['string'\] contains a Puppet::Util::Execution::ProcessOutput value. It will be converted to the String 'test'/)
-      end
-    end
-
     it "should ensure all values to be printed are in the external encoding" do
       resources = [
         Puppet::Type.type(:user).new(:name => "\u2603".force_encoding(Encoding::UTF_8)).to_resource,