This message was deleted.

Could the problem be related to the recent (Oct 2022) change for structured Aliases? https://github.com/pulumi/pulumi/commit/95e2505de5a42ae9ae51dfa31371b8850d493716#diff-37dfa20e31314a0c7725fcbfead[…]9da36757214fa12ca9653d018ceb58f8

Interesting idea, @clever-application-67149 - worth trying Pulumi 3.42.0 then 3.43.0, since latter is release where structured aliases were added: https://github.com/pulumi/pulumi/releases/tag/v3.43.0 (only a Python related fix in 3.43.1)

@salmon-gold-74709, I had been downgrading Pulumi but had only gotten to 3.49.0. I downgraded to 3.42.0 and the

No valid 'type' passed in for alias

error is gone, but now I have a serialization error on the same `awsacm/certificateCertificate`:

error: Error: failed to register new resource artemis-dev-support-cert [aws:acm/certificate:Certificate]: 13 INTERNAL: Request message serialization failure: Assertion failed: Expected string but got %s: %s.
        at Object.registerResource (/home/labuser/.cache/bazel/_bazel_labuser/34360f705a4b3bbdc2679b46775386d6/execroot/artemis/node_modules/@pulumi/aws/node_modules/@pulumi/runtime/resource.ts:339:27)
        at new Resource (/home/labuser/.cache/bazel/_bazel_labuser/34360f705a4b3bbdc2679b46775386d6/execroot/artemis/node_modules/@pulumi/aws/node_modules/@pulumi/resource.ts:398:13)
        at new CustomResource (/home/labuser/.cache/bazel/_bazel_labuser/34360f705a4b3bbdc2679b46775386d6/execroot/artemis/node_modules/@pulumi/aws/node_modules/@pulumi/resource.ts:782:9)
        at new Certificate (/home/labuser/.cache/bazel/_bazel_labuser/34360f705a4b3bbdc2679b46775386d6/execroot/artemis/node_modules/@pulumi/acm/certificate.ts:334:9)
        at CertificateManager.getCert (/home/labuser/.cache/bazel/_bazel_labuser/34360f705a4b3bbdc2679b46775386d6/execroot/artemis/bazel-out/k8-fastbuild/bin/infrastructure/infrastructure/artemis/src/aws/certificate.ts:36:18)
        at new SupportCloudFront (/home/labuser/.cache/bazel/_bazel_labuser/34360f705a4b3bbdc2679b46775386d6/execroot/artemis/bazel-out/k8-fastbuild/bin/infrastructure/infrastructure/artemis/src/aws/cloudfront/support.ts:64:44)
        at Injector.instantiateClass (/home/labuser/.cache/bazel/_bazel_labuser/34360f705a4b3bbdc2679b46775386d6/execroot/artemis/bazel-out/k8-fastbuild/bin/infrastructure/node_modules/@nestjs/core/injector/injector.js:330:19)
        at callback (/home/labuser/.cache/bazel/_bazel_labuser/34360f705a4b3bbdc2679b46775386d6/execroot/artemis/bazel-out/k8-fastbuild/bin/infrastructure/node_modules/@nestjs/core/injector/injector.js:48:41)
        at Injector.resolveConstructorParams (/home/labuser/.cache/bazel/_bazel_labuser/34360f705a4b3bbdc2679b46775386d6/execroot/artemis/bazel-out/k8-fastbuild/bin/infrastructure/node_modules/@nestjs/core/injector/injector.js:122:24)
        at Injector.loadInstance (/home/labuser/.cache/bazel/_bazel_labuser/34360f705a4b3bbdc2679b46775386d6/execroot/artemis/bazel-out/k8-fastbuild/bin/infrastructure/node_modules/@nestjs/core/injector/injector.js:52:9)

Now what? Do I need to downgrade

@pulumi/aws

and

@pulumi/awsx

as well?

Best to re-test with 3.43.0 - assuming that shows original error, I would log a GitHub issue about the aliases error