Page MenuHomeDevCentral

Ensure webserver-content index can always be regenerated
ClosedPublic

Authored by dereckson on Jun 12 2024, 18:55.
Tags
None
Referenced Files
F45143857: D3330.id8566.diff
Thu, Aug 20, 11:05
F45136727: D3330.id8563.diff
Thu, Aug 20, 10:12
F45136436: D3330.diff
Thu, Aug 20, 10:10
F45136354: D3330.id8564.diff
Thu, Aug 20, 10:10
Unknown Object (File)
Tue, Aug 18, 13:26
Unknown Object (File)
Tue, Aug 18, 06:14
Unknown Object (File)
Tue, Aug 18, 04:40
Unknown Object (File)
Tue, Aug 18, 02:47
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