Add api_id to the client output file amplify_outputs.json.

[michael-trinity]

Problem

Using DBB in lambda would result in issues since the table names generated contain the api_id

Issue number, if available:

Changes

Added the api_id to the json output file so it can be used for the dynamically generated tables.

Corresponding docs PR, if applicable:

Validation

I'm using the changed files myself currently to generate the needed file.

I tested it with this lambda code

import { DynamoDBClient } from "@aws-sdk/client-dynamodb"; import { DynamoDBDocumentClient, TransactWriteCommand } from "@aws-sdk/lib-dynamodb";

import config from '../../../../amplify_outputs.json';

const client = new DynamoDBClient({});
const docClient = DynamoDBDocumentClient.from(client);

const createTableName = (name: string) => {
    return `${name}-${config.data.api_id}-NONE`;
}

export const handler = async (event: any) => {
    const { userId, amount } = event.arguments;

    const transactItems = [
        // Update UserProfile
        {
            Update: {
                TableName: createTableName('UserProfile'),
                Key: { id: userId },
                UpdateExpression: 'ADD currentPoints :pointsToAdd',
                ExpressionAttributeValues: { ':pointsToAdd': amount }
            }
        }
    ];

    try {
        const results = await docClient.send(new TransactWriteCommand({ TransactItems: transactItems }));

        console.log(results)

        return results['$metadata']
    } catch (error) {
        console.error('Error:', error);
        throw new Error('Failed to process the transaction');
    }
};

Checklist

• If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
• If this PR requires a change to the Project Architecture README, I have included that update in this PR.
• If this PR requires a docs update, I have linked to that docs PR above.
• If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d7c5f70

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR