Documentation
¶
Overview ¶
Command e2e-https-server serves files for the acceptance phase and the runner harness rows that read schemas and migration directories from an HTTPS download pinned by its digest.
It serves every file of one directory, read again on every request, so a phase replaces a download's bytes by editing the ConfigMap the directory is mounted from. The first path element says how a file is reached:
/public/<file> no credential /basic/<file> HTTP Basic, the user and password the flags name /bearer/<file> a Bearer token /same/<prefix>/... a redirect to /<prefix>/... on the host the client asked /away/<prefix>/... a redirect to /<prefix>/... on the other origin
Every request is logged, and GET /requests answers the log as JSON, so a phase can show that a host or a path received nothing. The digest of every file is logged when the server starts and whenever the file changes, so a phase that replaced a download's bytes knows when the server serves them.
Click to show internal directories.
Click to hide internal directories.