Page MenuHomePhabricator

[Nix] Provide default for squadcal_url.json
ClosedPublic

Authored by jon on Dec 8 2022, 11:43 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 11, 7:03 AM
Unknown Object (File)
Fri, Nov 8, 10:00 AM
Unknown Object (File)
Thu, Nov 7, 5:48 AM
Unknown Object (File)
Mon, Nov 4, 4:02 PM
Unknown Object (File)
Mon, Nov 4, 4:02 PM
Unknown Object (File)
Tue, Oct 22, 5:16 PM
Unknown Object (File)
Tue, Oct 22, 5:16 PM
Unknown Object (File)
Tue, Oct 22, 5:16 PM
Subscribers

Details

Summary

Add squalcal_url.json default with other facts.

squalcal_url.json is being used a fallback router for "/" in
this regard.

May be redundant with D5846, but aligns with intent.

https://linear.app/comm/issue/ENG-2260

Depends on D5846

Test Plan
rm keyserver/facts/*.json

nix develop

# Assert files were written, and content matches scripts/templates
ls keyserver/facts
cat keyserver/facts/*.json

Diff Detail

Repository
rCOMM Comm
Branch
jonringer/nix-squadcal (branched from master)
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

Not redundant – the migration won't run when initializing a new environment

ashoat requested changes to this revision.Dec 13 2022, 9:56 AM
ashoat added inline comments.
scripts/templates/squadcal_url.json
6 ↗(On Diff #19260)

This needs proxy: "apache"

This revision now requires changes to proceed.Dec 13 2022, 9:56 AM

I would really love for the Test Plan to actually test the Apache configuration to make sure it works. Is this handled somewhere else, or are we just hoping it works, and hoping that your reviewers will catch any errors?

This revision is now accepted and ready to land.Dec 15 2022, 9:27 AM
jon retitled this revision from [Nix] Provide default for squalcal_url.json to [Nix] Provide default for squadcal_url.json.Dec 15 2022, 9:40 AM

Update template with settings from D5846

I would really love for the Test Plan to actually test the Apache configuration to make sure it works. Is this handled somewhere else, or are we just hoping it works, and hoping that your reviewers will catch any errors?

Tested this with the migration workflow in D5846. Just couldn't do my testing until I was able to re-create the apache workflow reliably.

The native iOS application seems to dynamically pick the changes from D5846, so this shouldn't be too much of an issue after D5846 lands.