Page MenuHomeDevCentral

Ensure webserver-content index can always be regenerated
ClosedPublic

Authored by dereckson on Jun 12 2024, 18:55.
Tags
None
Referenced Files
F3783580: D3330.id8563.diff
Tue, Nov 26, 03:50
F3783291: D3330.id8566.diff
Tue, Nov 26, 02:51
F3783290: D3330.id8564.diff
Tue, Nov 26, 02:51
F3783289: D3330.id8563.diff
Tue, Nov 26, 02:50
F3783252: D3330.id.diff
Tue, Nov 26, 02:43
F3783232: D3330.diff
Tue, Nov 26, 02:39
Unknown Object (File)
Sat, Nov 23, 10:05
Unknown Object (File)
Sat, Nov 23, 10:05
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