No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Morning.
AWS Layer Extensions are up and running and they cause some logical issues with Pulumi. Say we install the Layer extension for Lumigo or Sentry, they automatically add environment variables and layers to the selected lambdas.

Pulumi however does not recognize these and attempts to delete those when running `pulumi up`. Is there any way we can easily configure it so that Pulumi won’t attempt to delete those? Perhaps there is an easy way to import the configurations instead?