Pahud Hsieh

Results 356 comments of Pahud Hsieh

## Current vs Expected Behavior ### Current Behavior (defineStorage + Custom CDK) ```typescript // User defines storage export const storage = defineStorage({ name: "myStorage", access: (allow) => ({ "images/*": [allow.authenticated.to(["read",...

## Current vs Expected Behavior ### Current Behavior (Problematic) ```typescript // User adds field to existing model in resource.ts SCResponses: a .model({ id: a.id().required(), // ... existing fields signature: a.string().required(),...

## Current vs Expected Behavior ### Current Behavior (Documentation Gap) ```mermaid flowchart TD subgraph "Current Documentation State" A[Custom Functions Docs] --> B[Python Examples ✓] A --> C[Go Examples ✓] A...

try run ```sh $ yarn integ test/aws-stepfunctions-tasks/test/batch/integ.run-batch-job.js --update-on-failed --disable-update-workflow $ yarn integ test/aws-stepfunctions-tasks/test/batch/integ.submit-job.js --update-on-failed --disable-update-workflow ``` to update the snapshots

## Current vs Expected Behavior ### Current Behavior ```typescript // team-provider-info.json contains account-specific information { "dev": { "awscloudformation": { "AuthRoleName": "amplify-myapp-dev-123456-authRole", "UnauthRoleArn": "arn:aws:iam::123456789012:role/amplify-myapp-dev-123456-unauthRole", "AuthRoleArn": "arn:aws:iam::123456789012:role/amplify-myapp-dev-123456-authRole", "Region": "us-east-1", "DeploymentBucketName": "amplify-myapp-dev-123456-deployment", "UnauthRoleName":...

Hi @tomburge, Thank you for reporting this issue. This is a valid concern regarding tag propagation in the EKS v2 alpha module. **Problem Confirmed**: Custom resources created by EKS v2...

## Current vs Expected Behavior ### Current Behavior ```typescript // When using @searchable directive in GraphQL schema type Post @model @searchable { id: ID! title: String! content: String! } ```...

Hi @houmark I just escalated this issue to P1. I’ll bring it up with the team tomorrow to make sure it’s addressed promptly.

The PR has been merged https://github.com/aws-amplify/amplify-category-api/pull/3338 https://github.com/aws-amplify/amplify-category-api/pull/3340 I will request internally if there's any timelines we can share for the next release.

AFAIK we are actively working on this. I'll connect with @svidgen for inputs.