Continue configuring in the normal way

[t0yv0]

@blampe points out in pulumi/pulumi-go-provider#172 it's might not be necessary to marshal with configencoding once we get past CheckConfig. Interesting idea. This works fine for a simple program on custom AWS build:

name: aws-yaml-configs
runtime: yaml
description: A minimal AWS Pulumi YAML program
outputs:
  # Export the name of the bucket
  bucketName: ${my-bucket.id}
resources:
  provider:
    type: pulumi:providers:aws
    properties:
      defaultTags:
        tags:
          foo: bar
    options:
      version: 6.17.0
  my-bucket:
    type: aws:s3:Bucket
    options:
      provider: ${provider}

Let me think of further testing. This can improve granularity of secret tracking.

[t0yv0]

This is now UnknownObjectValue = "dd056dcd-154b-4c76-9bd3-c8f88648b5ff" ... ever so slightly weird.

[t0yv0]

This is great - improved granularity of secret marking.