schema: Add known_fingerprints option to schema command

When client requests schema it can list fingerprints of cached schemas
and server responds with SchemaUpToDate exception specifying fingeprint
of schema to use.

https://fedorahosted.org/freeipa/ticket/4739

Reviewed-By: Jan Cholasta <jcholast@redhat.com>

1 files changed, 18 insertions, 0 deletions

diff --git a/ipalib/errors.py b/ipalib/errors.py
index bd2d314a4..10491a942 100644
--- a/ipalib/errors.py
+++ b/ipalib/errors.py
@@ -1820,6 +1820,24 @@ class CertificateInvalidError(CertificateError):
     format = _('%(name)s certificate is not valid')
 
 
+class SchemaUpToDate(ExecutionError):
+    """
+    **4311** Raised by server when client asks for metadata but
+    already has current version. Exception's attribute 'fingerprint'
+    identitfies schema version to use. Attribute 'ttl' specifies how
+    long (in seconds) before client should check for schema update.
+
+    For example:
+    >>> raise SchemaUpToDate(fingerprint=u'deadbeef', ttl=3600)
+    Traceback (most recent call last):
+      ...
+    SchemaUpToDate: Schema is up to date (FP 'deadbeef', TTL 3600 s)
+    """
+
+    errno = 4311
+    format = _("Schema is up to date (FP '%(fingerprint)s', TTL %(ttl)s s)")
+
+
 class DNSError(ExecutionError):
     """
     **4400** Base class for DNS execution errors (*4400 - 4499*).