given this ```export const ymml = new k8s yaml ConfigFile ya

Question

given this ```export const ymml = new k8s yaml ConfigFile yamlfile file foo yaml ``` and a test like this ``` describe yaml function it reads function done pulumi all infra ymml urn infra ymml apply urn thefile = gt console log urn var val = thefile getResource v1 Service my service console log val done ``` in a unit test is there away to see the output of the file At the moment I get this ```yaml urn pulumi stack project kubernetes yaml ConfigFile yamlfile OutputImpl pulumiOutput true resources Function anonymous allResources Function anonymous isKnown Promise lt pending gt isSecret Promise lt pending gt promise Function anonymous toString Function anonymous toJSON Function anonymous reads node 58505 PromiseRejectionHandledWarning Promise rejection was handled asynchronously rejection id 3 Use `node trace warnings ` to show where the warning was created node 58505 PromiseRejectionHandledWarning Promise rejection was handled asynchronously rejection id 4 ``` I am trying to understand an error that looks like this when running that deploys a blackbox exporter I can apply it using `kubectl apply` but it s failing as below in pulumi `Error invocation of kubernetes yaml decode returned an error error converting YAML to JSON yaml control characters are not allowed`

little-cartoon-10569 · Answer

I convert outputs like this to promises then use the ChaiAsExpected library to achieve it The alternative is to have all your expects shoulds inside `apply ` blocks and that s a bit tricky to synchonize properly

little-cartoon-10569 · Answer

However if all you want to do is log the val to the console use `val apply contents = gt console log contents `

stocky-france-59380 · Answer

<https github com pulumi pulumi issues 5924> what s being talked about here w r t using promises on outputs

little-cartoon-10569 · Answer

Can you rephrase the question

little-cartoon-10569 · Answer

There is an internal Pulumi function that immediately returns a Promise from an Output This is described in the GitHub issue It can be useful when unit testing because there are unit testing libraries that support Promises but none that support Outputs

little-cartoon-10569 · Answer

The alternative is to make your unit test fully async which Jest and Mocha support and probably all common libraries and do your assertions inside `apply ` blocks

little-cartoon-10569 · Answer

However your original question seems only to want to know how to look at the contents of an output rather than how to assert on them

little-cartoon-10569 · Answer

In which case simply moving your log statement into the apply block is all you need to do

stocky-france-59380 · Answer

Will you share a code sample of how you assert with ChaiAsExpected that you mentioned above

little-cartoon-10569 · Answer

Sure onesec

stocky-france-59380 · Answer

found my problem using this Copy pasted content into a new file The problem file was initialiy created using an io redirect ` gt ` ```const yaml = require js yaml const fs = require fs describe js yaml function it read function done let fileContent = fs readFileSync foo yml utf 8 let data = yaml load fileContent console log data done ```

stocky-france-59380 · Answer

I do not appear to be getting output to the console using this snippet ``` describe yaml function it reads function done pulumi all infra ymml urn infra ymml apply urn thefile = gt console log urn var val = thefile getResource v1 Service my service val apply content = gt console log content apiVersion done ``` where `foo yaml` looks like this ```apiVersion v1 kind Service metadata name my service spec selector app MyApp ports protocol TCP port 80 targetPort 9376``` the output is ``` yaml urn pulumi stack project kubernetes yaml ConfigFile yamlfile reads node 72056 PromiseRejectionHandledWarning Promise rejection was handled asynchronously rejection id 3 Use `node trace warnings ` to show where the warning was created node 72056 PromiseRejectionHandledWarning Promise rejection was handled asynchronously rejection id 4 ```

little-cartoon-10569 · Answer

Sorry my internet has died on phone atm

little-cartoon-10569 · Answer

The problem with using apply in tests is that the tests may finish before the promise resolves Or as in this case the promise may be rejected leaving you with very little information

little-cartoon-10569 · Answer

I think you need to add `async` to the function you pass to `it`

little-cartoon-10569 · Answer

It s not waiting for the apply to finish