Christoffer Rehn

@justinwb No major updates just yet, but I've opened https://github.com/aws-actions/setup-sam/pull/70, which adds support for using the native installers (i.e. without needing Python separately, or `pip`), making installs a lot faster,...

> > @justinwb No major updates just yet, but I've opened #70, which adds support for using the native installers (i.e. without needing Python separately, or `pip`), making installs a...

With https://github.com/aws-actions/setup-sam/pull/73 merged, if you have `use-installer: true` and specify the `version`, it'll cache the SAM CLI for future use. This is beneficial for self-hosted runners. It doesn't currently cache...

Resolving this in favor of the more granular https://github.com/aws-actions/setup-sam/issues/76 as caching is now supported with `use-installer` and `version`.

Any updates to this? Why doesn’t the generated schema specify which standard it adheres to?

We could perhaps allow omitting properties in the event that can be determined from the OpenAPI definition; marking as feature request.

> Is anyone working on this? I'm seemingly unable to define API endpoints in nested stacks because importing the API (AWS::Serverless::Api) from the parent stack doesn't work (resulting in "RestApiId...

@tariromukute The issue seems to be that the intrinsic function must be resolved before deployment (local paths are unsupported by CloudFormation; under the hood SAM CLI uploads the assets and...

@tariromukute You have to use SAM CLI to deploy any templates with local paths (such as most `sam init` templates), as SAM CLI needs to upload the assets first. As...

@tariromukute If I'm understanding correctly the problem you're encountering is `!Ref` to local paths in `AWS::Serverless::LayerVersion` not working. I was able to reproduce it, and confirmed it works with `CodeUri`...