You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- CURSOR_SUMMARY -->
> [!NOTE]
> Move S3 credential handling to runtime with
`resolve_s3_credentials_from_env`, add `resolve_credentials` to
`load_from_user_code`, and set context-specific env/flags across CLI,
planning, and TS/Py libs.
>
> - **Core (InfrastructureMap)**:
> - Add `resolve_s3_credentials_from_env()` to resolve S3/S3Queue creds
from env at runtime and recalc `engine_params_hash`.
> - Change `load_from_user_code(project, resolve_credentials)` and
optionally resolve creds; propagate throughout callers.
> - Planning (`plan.rs`): load prebuilt JSON (no creds) in prod when
present, then ALWAYS resolve creds at runtime; when building from code,
pass `true`.
> - **Partial Map (DMV2)**:
> - Keep S3/S3Queue env markers in engine configs; remove build-time
secret resolution helper.
> - **CLI commands**:
> - Pass resolve flag appropriately:
> - Runtime ops use `true`: `remote_plan`, `remote_gen_migration`,
`remote_refresh`, `migrate`, workflows, seed data.
> - Structure-only ops use `false`: `check` (and JSON write), `db pull`,
`ls`, `kafka pull`.
> - **Executors**:
> - Set `IS_LOADING_INFRA_MAP=true` when running TS `dmv2-serializer`
and Python serializer to emit markers during infra loading.
> - **Language libs (secrets)**:
> - TS/Py `mooseRuntimeEnv.get()`/`get()` now return markers when
`IS_LOADING_INFRA_MAP=true`, otherwise fetch real env vars (error if
unset); tests updated.
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
67dc4cc. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
0 commit comments