Page MenuHomeDevCentral

Ensure webserver-content index can always be regenerated
ClosedPublic

Authored by dereckson on Jun 12 2024, 18:55.
Tags
None
Referenced Files
F29549581: D3330.id8566.diff
Mon, May 18, 06:40
F29548581: D3330.id8563.diff
Mon, May 18, 06:33
F29540375: D3330.id8564.diff
Mon, May 18, 05:25
F29538370: D3330.id.diff
Mon, May 18, 05:12
F29533363: D3330.diff
Mon, May 18, 04:43
F29528506: D3330.diff
Mon, May 18, 04:08
F29498835: D3330.id.diff
Mon, May 18, 00:20
F29482950: D3330.id8564.diff
Sun, May 17, 21:56
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