diff options
author | Lars Wirzenius <liw@liw.fi> | 2021-08-02 07:13:42 +0000 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2021-08-02 07:13:42 +0000 |
commit | aa7812a971f35fcb217a3e115f06a51f3706f5ca (patch) | |
tree | 4e67ca7a802fe50477f4039a27214401af68bafe /obnam.md | |
parent | 8c2f79fa3cecadd8e7d7f74df6938b25c81c5e9e (diff) | |
parent | 9f8e448153b9b35a36063c5a2a659c139ff0e31d (diff) | |
download | obnam2-aa7812a971f35fcb217a3e115f06a51f3706f5ca.tar.gz |
Merge branch 'feature/117-obnam_server_log' into 'main'
feat: configure log verbosity with OBNAM_SERVER_LOG envvar
Closes #117
See merge request obnam/obnam!170
Diffstat (limited to 'obnam.md')
-rw-r--r-- | obnam.md | 25 |
1 files changed, 25 insertions, 0 deletions
@@ -1124,6 +1124,31 @@ and chunk-meta is {"sha256":"abc","generation":null,"ended":null} and the body matches file data.dat ~~~ + +## Obeys `OBNAM_SERVER_LOG` environment variable + +The chunk server logs its actions to stderr. Verbosity of the log depends on the +`OBNAM_SERVER_LOG` envvar. This scenario verifies that the variable can make the +server more chatty. + +~~~scenario +given an installed obnam +and a running chunk server +and a file data1.dat containing some random data +when I POST data1.dat to /chunks, with chunk-meta: {"sha256":"qwerty"} +then the JSON body has a field chunk_id, henceforth ID +and chunk server's stderr doesn't contain "Obnam server starting up" +and chunk server's stderr doesn't contain "created chunk <ID>" + +given a running chunk server with environment {"OBNAM_SERVER_LOG": "info"} +and a file data2.dat containing some random data +when I POST data2.dat to /chunks, with chunk-meta: {"sha256":"xyz"} +then the JSON body has a field chunk_id, henceforth ID +and chunk server's stderr contains "Obnam server starting up" +and chunk server's stderr contains "created chunk <ID>" +~~~ + + # Acceptance criteria for the Obnam client The scenarios in chapter verify that the Obnam client works as it |