Page MenuHomeDevCentral

Ensure webserver-content index can always be regenerated
ClosedPublic

Authored by dereckson on Jun 12 2024, 18:55.
Tags
None
Referenced Files
F6814351: D3330.diff
Sat, Apr 12, 16:40
F6813021: D3330.id8566.diff
Sat, Apr 12, 12:56
F6813006: D3330.id8566.diff
Sat, Apr 12, 12:52
F6812903: D3330.id8564.diff
Sat, Apr 12, 12:32
F6812844: D3330.id8564.diff
Sat, Apr 12, 12:26
F6812471: D3330.id8566.diff
Sat, Apr 12, 10:55
F6810533: D3330.id8564.diff
Sat, Apr 12, 04:10
Unknown Object (File)
Fri, Apr 11, 12:32
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 Passed
Unit
No Test Coverage
Branch
main
Build Status
Buildable 5269
Build 5550: arc lint + arc unit