SUMMARY

When provisioning aws_lambda_function and attaching aws_lambda_provisioned_concurrency_config on initial provision the aws_lambda_provisioned_concurrency_config expects a published version, this is not done in time for aws_lambda_provisioned_concurrency_config to recognize the published version.

Expected results

When provisioning a new aws_lambda_function it publishes a new version attaches to an alias and successfully provisions

What actually happens:

{
  Message_: "Provisioned Concurrency Configs cannot be applied to unpublished function versions.",
  Type: "User"
}

POTENTIAL FIX

When aws Lambda provisions make it so that publish = true is required before aws_lambda_provisioned_concurrency_config can be provisioned