Page MenuHomeDevCentral

Ensure webserver-content index can always be regenerated
ClosedPublic

Authored by dereckson on Jun 12 2024, 18:55.
Tags
None
Referenced Files
F44279750: D3330.id8563.diff
Sun, Aug 16, 08:33
F44279736: D3330.id8564.diff
Sun, Aug 16, 08:33
F44279720: D3330.id8566.diff
Sun, Aug 16, 08:33
F44252039: D3330.id.diff
Sun, Aug 16, 05:30
F44240419: D3330.diff
Sun, Aug 16, 04:16
Unknown Object (File)
Mon, Aug 10, 15:09
Unknown Object (File)
Mon, Aug 10, 03:34
Unknown Object (File)
Sun, Aug 9, 20:44
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