Project

General

Profile

Actions

User story #3403

closed

User story #3231: Validation workflows for configuration related change request

Create a migration script to allow the usage of workflow in Rudder

Added by Vincent MEMBRÉ about 11 years ago. Updated about 9 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Since the workflow are almost completed for 2.6.0, we know what will be important for the migration script:

One part consists in adding the new table in Rudder psql database,

the file 'dbMigration-2.5-2.6-add_workflow_support.sql' contains the following sql commands

create sequence ChangeRequestId start 1;

CREATE TABLE ChangeRequest(
  id        integer PRIMARY KEY default(nextval('ChangeRequestId'))
, name text CHECK (name <> '')
, description text
, creationTime timestamp with time zone
, content xml
);

CREATE TABLE Workflow(
  id integer references ChangeRequest(id)
, state text
);

the other consists in handling the properties

  • commenting "rudder.autoDeployOnModification" because it will not be in usage anymore
  • adding the property "rudder.workflow.enabled" and set it to
    • false if rudder.autoDeployOnModification was true (no workflow if change were automatically deployed)
    • true if rudder.autoDeployOnModification was false
Actions

Also available in: Atom PDF