-
Notifications
You must be signed in to change notification settings - Fork 0
chore: rename pipeline/run to redaction job terminology #100
Copy link
Copy link
Open
Labels
choremaintenance, dependency updates, code cleanupmaintenance, dependency updates, code cleanupnatsnvisy-nats: messaging, job queues, object storagenvisy-nats: messaging, job queues, object storagepostgresnvisy-postgres: ORM, models, queries, migrationsnvisy-postgres: ORM, models, queries, migrationsservernvisy-server: API handlers, middleware, authnvisy-server: API handlers, middleware, auth
Metadata
Metadata
Assignees
Labels
choremaintenance, dependency updates, code cleanupmaintenance, dependency updates, code cleanupnatsnvisy-nats: messaging, job queues, object storagenvisy-nats: messaging, job queues, object storagepostgresnvisy-postgres: ORM, models, queries, migrationsnvisy-postgres: ORM, models, queries, migrationsservernvisy-server: API handlers, middleware, authnvisy-server: API handlers, middleware, auth
Type
Fields
Give feedbackNo fields configured for issues without a type.
Context
The pipeline and pipeline run handlers use ETL-era naming. These should be reframed as redaction jobs/runs to align with the platform's redaction focus.
Requirements
pipelinestojobs(orredaction-jobs) across handlers, request/response types, database models, and API pathspipeline_runstoruns(orjob-runs)References