Page MenuHomeDevCentral

Ensure webserver-content index can always be regenerated
ClosedPublic

Authored by dereckson on Jun 12 2024, 18:55.
Tags
None
Referenced Files
F25102804: D3330.id8563.diff
Mon, Mar 30, 05:41
F25100033: D3330.id8563.diff
Mon, Mar 30, 02:00
F25099659: D3330.id8563.diff
Mon, Mar 30, 01:26
F25099605: D3330.id8563.diff
Mon, Mar 30, 01:21
F25099598: D3330.id8566.diff
Mon, Mar 30, 01:21
F25097507: D3330.id8564.diff
Sun, Mar 29, 22:10
F25095414: D3330.id8566.diff
Sun, Mar 29, 18:31
F25094999: D3330.id8564.diff
Sun, Mar 29, 17:30
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 Not Applicable
Unit
Tests Not Applicable