rm CATCHUP_ETL_ARN#229
Conversation
Hurshal Patel (choochootrain)
requested review from
Kevin Green (KevinGreen) and
Mike Deeks (mdeeks)
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a8038784f9
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "Codex (@codex) address that feedback".
| AI_PROXY_FN_ARN = aws_lambda_function.ai_proxy.arn | ||
| AI_PROXY_FN_URL = aws_lambda_function_url.ai_proxy.function_url | ||
| AI_PROXY_INVOKE_ROLE = aws_iam_role.ai_proxy_invoke_role.arn | ||
| CATCHUP_ETL_ARN = aws_lambda_function.catchup_etl.arn | ||
| INSERT_LOGS2 = "true" |
There was a problem hiding this comment.
This change removes CATCHUP_ETL_ARN from the API handler’s default environment, which is the only in-module wiring from APIHandler to the Catchup ETL Lambda. The API handler role still includes a dedicated CatchupETLInvoke permission (modules/services/iam.tf lines 35-38), so the runtime path is still expected to invoke that function; without this env var, deployments using that path can fail at runtime unless operators manually re-add it via extra_env_vars.APIHandler.
Useful? React with 👍 / 👎.
2 participants
do not merge until confirmed