Problem/Motivation

When a workspace is published, we need the option of storing long term data that capture either the specific revision ids being published, or all revision ids of all entities that will be published after this workspace is deployed.

Also allow this option to be overridden when a workspace gets published if corresponding setting is active.

Proposed resolution

Extend the settings form with options for these requirements and allow overriding them with the same mechanism as was implemented in https://git.drupalcode.org/project/wse/-/commit/75ea4f8

Storage for saving these revision ids in custom table with fields: workspace_id, workspace_label, date_of_publish, revision_ids (blob). On workspace entity delete, cleanup this table.

Issue fork wse-3233413

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

s_leu created an issue. See original summary.

s_leu’s picture

Status: Active » Needs review

amateescu’s picture

Status: Needs review » Fixed

Merged into 1.0.x, thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.