pulumi

• Fix SxS issue introduced in 1.7.0 when assigning Outputs across different versions of the @pulumi/pulumi SDK. #3658

• A Pulumi JavaScript/TypeScript program can now consist of a single exported top level function. This allows for an easy approach to create a Pulumi program that needs to perform async/await operations at the top-level. #3321

  // JavaScript
  module.exports = async () => {
  }
  
  //TypeScript
  export = async () => {
  }
  

• Support passing a parent and providers for ReadResource, RegisterResource, and Invoke in the go SDK. #3563

• Fix go SDK ReadResource. #3581

• Fix go SDK DeleteBeforeReplace. #3572

• Support for setting the PULUMI_PREFER_YARN environment variable to opt-in to using yarn instead of npm for installing Node.js dependencies. #3556

• Fix regression that prevented relative paths passed to --policy-pack from working. #3565

• Support for config.GetObject and related variants for Golang. #3526

• Add support for IgnoreChanges in the go SDK. #3514

• Support for a go run style workflow. Building or installing a pulumi program written in go is now optional. #3503

• Re-apply "propagate resource inputs to resource state during preview, including first-class unknown values." The new set of changes have additional fixes to ensure backwards compatibility with earlier code. This allows the preview to better estimate the state of a resource after an update, including property values that were populated using defaults calculated by the provider. #3327

• Validate StackName when passing a non-default secrets provider to pulumi stack init

• Add support for go1.13.x

• pulumi update --target and pulumi destroy --target will both error if they determine a dependent resource needs to be updated, destroyed, or created that was not was specified in the --target list. To proceed with an update/destroy after this error, either specify all the reported resources as --targets, or pass the --target-dependents flag to allow necessary changes to unspecified dependent targets.

• Support for node 13.x, building with gcc 8 and newer. [#3512] (https://github.com/pulumi/pulumi/pull/3512)

• Codepaths which could result in a hang will print a message to the console indicating the problem, along with a link to documentation on how to restructure code to best address it.

Compatibility

• StackReference.getOutputSync and requireOutputSync are deprecated as they may cause hangs on some combinations of Node and certain OS platforms. StackReference.getOutput and requireOutput should be used instead.