Page MenuHomeDevCentral

Ensure webserver-content index can always be regenerated
ClosedPublic

Authored by dereckson on Jun 12 2024, 18:55.
Tags
None
Referenced Files
F23684915: D3330.id8566.diff
Fri, Feb 6, 01:38
F23676691: D3330.id8563.diff
Fri, Feb 6, 00:46
F23667829: D3330.id8566.diff
Thu, Feb 5, 23:44
F23639467: D3330.id8566.diff
Thu, Feb 5, 20:16
F23636331: D3330.id8564.diff
Thu, Feb 5, 19:55
F23635825: D3330.id8563.diff
Thu, Feb 5, 19:52
F23624367: D3330.id8566.diff
Thu, Feb 5, 18:31
F23621292: D3330.id8563.diff
Thu, Feb 5, 18: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