Rob Crittenden b842b825ab Make the schema cache TTL user-configurable ... The API schema is not checked for changes until after a TTL is expired. A one-hour TTL was hardcoded which makes development tedious because the only way to force a schema update is to remember to remove files between invocations. This adds a new environment variable, schema_ttl, to configure the TTL returned by the server to schema() calls. This can be set low to ensure a frequent refresh during development. If the client is in compat mode, that is if client is working against a server that doesn't support the schema() command, then use the client's schema_ttl instead so that the user still has control. Re-check validity before writing the cache. This saves us both a disk write and the possibility of updating the expiration with a ttl of 0. This can happen if the fingerprint is still valid (not expired, no language change) the schema check is skipped so we have no server-provided ttl. https://pagure.io/freeipa/issue/8492 Signed-off-by: Rob Crittenden <rcritten@redhat.com> Reviewed-By: Stanislav Levin <slev@altlinux.org> Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com>		2021-11-03 10:59:10 +01:00
..
__init__.py	pytest 3.x compatibility	2017-03-27 18:03:14 +02:00
cmdline.py	pytest: Migrate unittest/nose to Pytest fixtures	2020-02-12 18:08:32 +02:00
test_cli.py	pytest: Migrate unittest/nose to Pytest fixtures	2020-02-12 18:08:32 +02:00
test_console.py	Make tab completion in console more useful	2020-07-07 12:36:10 +02:00
test_help.py	Address inconsistent-return-statements	2018-11-13 13:37:58 +01:00
test_ipagetkeytab.py	pytest: Migrate xunit-style setups to Pytest fixtures	2020-02-12 18:08:32 +02:00
test_schema.py	Make the schema cache TTL user-configurable	2021-11-03 10:59:10 +01:00