Managing site design changes

[sh8121att]

Once a site deployment starts, the design data for that site is locked as the base design (changeid = 0). Any changes on that are tracked separately as an effective diff. This allows additions/changes to be started without impacting the existing site.

Currently Drydock can manage the base design data and design change data, but it doesn't link a change to the base so that the 'diff' can be patched in to see the new effective design. Need to design and implement this relationship.

[jezogwza]

Does the diff generate an audit trail of changes . In the log/db/ anywhere?

[sh8121att]

Each design change is maintained separately - the original design, once locked, isn't changed. So you have two layers being managed separately, so the diff between them can be calculated at any time.

The original design would have no parent design. Each subsequent change would have a parent design identifying the previous design being modified. When deployment actions are started, a design ID is specified so Drydock knows what the desired target state is. The effective design for the site then is the union of all the changes being applied to the initial design. This is the as-designed state of the site.

Separately persisted is the site build showing the result of the last deployment action, including the design ID used. This is the as-built state of the site.