feature: Include environment_name prefix in state_id for schedules

Feature scope

API

Description

When you use the CLI to run a meltano run <tap> ... <target> command, the state id for that job will be automatically prefixed with the current environment. However, schedules do not behave this way, and they just use the schedule name as the state_id/job_name. I think this could result in a dev environment unintentionally overwriting prod state, if the two environments share a meltano system database.

I’d like it if schedules used an environment prefix as well. This would protect users from inadvertently altering state across environments.

The environment prefix behavior of meltano run is documented here, and I confirmed through a check in my own environment that v2.4.0 does not use environment prefixes for schedules, whether orchestrated or called via CLI (meltano schedule run).

Related:

• #6853

[tayloramurphy]

@aaronsteers I don’t have an immediate concern with that 👍

[tayloramurphy]

I confirmed through a check in my own environment that v2.4.0 does not use environment prefixes for schedules, whether orchestrated or called via CLI (meltano schedule run).

@qbatten this highlights the need for better versioned docs! cc @afolson @sbalnojan

Agreed that this would be a good feature to have. I wasn’t aware that schedule didn’t defer to meltano run for the state id. @pandemicsyn @aaronsteers is that your understanding of the behavior?