The add_job management command can create a job in the RAP controller/agent to be run on a backend without invoving job-server. This is useful locally, for creating test jobs without having to connect your local controller/agent to a running job-server. However, in production (even on the test backend), it's a pathway for bypassing the standard audit trail on job-server.
We should keep the management command, but make it only available locally. We could identify if we're running locally by setting a local-only env variable, or by checking for a production-only env variable, or by settings.DEBUG, or something else, TBD.
Probably keep this in the cli but remove the management command interface to it so it's not listed in the production management commands
The
add_jobmanagement command can create a job in the RAP controller/agent to be run on a backend without invoving job-server. This is useful locally, for creating test jobs without having to connect your local controller/agent to a running job-server. However, in production (even on the test backend), it's a pathway for bypassing the standard audit trail on job-server.We should keep the management command, but make it only available locally. We could identify if we're running locally by setting a local-only env variable, or by checking for a production-only env variable, or by settings.DEBUG, or something else, TBD.
Probably keep this in the cli but remove the management command interface to it so it's not listed in the production management commands