Page MenuHomeDevCentral

Allow update script to be used for init too
ClosedPublic

Authored by dereckson on Sun, Aug 30, 08:34.
Tags
None
Referenced Files
F47676249: D4201.id11020.diff
Tue, Sep 1, 13:10
F47676190: D4201.diff
Tue, Sep 1, 13:10
F47637727: D4201.diff
Tue, Sep 1, 07:08
F47610585: D4201.id11019.diff
Tue, Sep 1, 03:04
Unknown Object (File)
Mon, Aug 31, 14:09
Unknown Object (File)
Mon, Aug 31, 14:08
Unknown Object (File)
Mon, Aug 31, 14:07
Unknown Object (File)
Mon, Aug 31, 11:08
Subscribers
None
Tokens
"Y So Serious" token, awarded by dereckson.

Details

Summary

When site deployment instructions can cover in the same workflow
both the init and update cases, this change allows to only give
an update script. It will be used for both deployments.

That requires the script to be able to initialize and recreate
the main site directory too.

This avoids to add complexity in operations repository to copy
or symlink both the same script for both purposes.

Fixes T2356.

Test Plan
  • new unit tests have been provided
  • test with labs. in T2354

Diff Detail

Repository
rALK Alkane
Lint
No Lint Coverage
Unit
No Test Coverage
Branch
update-as-init-fallback
Build Status
Buildable 6854
Build 7142: arc lint + arc unit

Event Timeline

dereckson created this revision.

Code by Qwen3.8-Max
Review and dangling_init_symlink case by GPT-5.6-Sol

This revision is now accepted and ready to land.Sun, Aug 30, 18:30