Page MenuHomeDevCentral

Ensure webserver-content index can always be regenerated
ClosedPublic

Authored by dereckson on Jun 12 2024, 18:55.
Tags
None
Referenced Files
F10912724: D3330.id8563.diff
Mon, Aug 4, 23:59
F10910675: D3330.id.diff
Mon, Aug 4, 22:19
F10910668: D3330.id8563.diff
Mon, Aug 4, 22:19
F10902725: D3330.id8564.diff
Mon, Aug 4, 14:53
F10901795: D3330.id8564.diff
Mon, Aug 4, 13:50
F10900060: D3330.diff
Mon, Aug 4, 11:20
F10899831: D3330.id8564.diff
Mon, Aug 4, 10:49
Unknown Object (File)
Mon, Aug 4, 01:20
Subscribers
None

Details

Summary

Previously, to regenerate webserver-content index, the index
needed to be existing, so the header can be copied through.

This change allows to regenerate it from scratch.

It also provides a test to ensure the file is up-to-date.

This is a follow-up for 64b8181e37ad.

Test Plan

rm roles/webserver-content/init.sls && make

Diff Detail

Repository
rOPS Nasqueron Operations
Lint
Lint Passed
Unit
No Test Coverage
Branch
main
Build Status
Buildable 5268
Build 5549: arc lint + arc unit