Page MenuHomeDevCentral

Ensure webserver-content index can always be regenerated
ClosedPublic

Authored by dereckson on Jun 12 2024, 18:55.
Tags
None
Referenced Files
F32951570: D3330.id8566.diff
Sat, Jun 13, 16:00
F32951339: D3330.id.diff
Sat, Jun 13, 15:56
F32951127: D3330.id8566.diff
Sat, Jun 13, 15:53
F32950077: D3330.id8564.diff
Sat, Jun 13, 15:35
F32942953: D3330.diff
Sat, Jun 13, 13:19
F32938597: D3330.id8563.diff
Sat, Jun 13, 12:01
Unknown Object (File)
Sat, Jun 13, 00:25
Unknown Object (File)
Fri, Jun 12, 20:25
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