amplify-backend

amplify-backend copied to clipboard

[POC] Attempt to use data and auth as stack providers for function. This won't work.

1

## Problem Certain usage patterns of functions end up with `Caused By: ❌ Deployment failed: Error [ValidationError]: Circular dependency between resources:`. This happens is scenarios where it could have been...

sobolk

[POC] Put every function in own stack

1

## Problem Certain usage patterns of functions end up with `Caused By: ❌ Deployment failed: Error [ValidationError]: Circular dependency between resources:`. This happens is scenarios where it could have been...

sobolk

[POC] Use resource name to have functions in separate stacks.

1

## Problem Certain usage patterns of functions end up with `Caused By: ❌ Deployment failed: Error [ValidationError]: Circular dependency between resources:`. This happens is scenarios where it could have been...

sobolk

[POC] Use single stack for top level functions

1

## Problem Certain usage patterns of functions end up with `Caused By: ❌ Deployment failed: Error [ValidationError]: Circular dependency between resources:`. This happens is scenarios where it could have been...

sobolk

Feature: allow all optional props for the NodejsFunction CDK construct to be passed via defineFunction in @aws-amplify/backend-function

5

## Problem `defineFunction` does not allow all props available on [NodejsFunction](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda_nodejs.NodejsFunction.html) **Issue number, if available:** #1968 ## Changes - [Allow passing optional props to `NodejsFunction` via `defineFunction`](https://github.com/aws-amplify/amplify-backend/commit/0cd26c38c36c7d83579fa619443d1b224c9aa730) - [Add test...

ataylorme

Bundle Bedrock SDK in ai-constructs

1

## Problem **Issue number, if available:** ## Changes **Corresponding docs PR, if applicable:** ## Validation ## Checklist - [ ] If this PR includes a functional change to the runtime...

sobolk

adds architecture prop on defineFunction

1

## Problem Allows users to chooses between `x86_64` and `arm64` for the function. As arm64 could provide a better price and performance than the equivalent function running on x86_64 architecture...

ykethan

Build notifications have unescaped url

1

### Environment information ```plain text General ``` ### Describe the bug We have amplify branch deployments and their build notifications enabled. When pushing branches like feature/cool-thing, the deployment URL is...

cedWetzel

CDK warnings print twice in sandbox

1

### Environment information ```plain text System: OS: macOS 14.6.1 CPU: (10) arm64 Apple M1 Pro Memory: 133.30 MB / 32.00 GB Shell: /opt/homebrew/bin/fish Binaries: Node: 20.16.0 - ~/.local/state/fnm_multishells/85211_1724692313979/bin/node Yarn: undefined...

josefaidt

### Description we should expand this [amplify_outputs test](https://github.com/aws-amplify/amplify-backend/blob/90eb24fdd7d8dfbe71e9756cd7b9bcae3391323f/.github/workflows/health_checks.yml#L278-L297) to cover programmatic read of outputs. It would prevent us from launching breaking backwards incompatible changes. (See example [here](https://github.com/aws-amplify/amplify-backend/blob/90eb24fdd7d8dfbe71e9756cd7b9bcae3391323f/.github/workflows/health_checks.yml#L151) where we assert...

Amplifiyer