#8492 RFE: Include the server schema version in communication with the client
Closed: fixed 2 years ago by frenaud. Opened 3 years ago by rcritten.

Request for enhancement

The lightweight client caches the available commands on the server and the i18n labels and such for displaying the return values.

The cache is updated periodically but there is no active checking to see if something has changed.

A user reported that their custom plugin label was not showing on a client until "after dinner", so I guess the schema expired and was refreshed and therefore the correct output was shown.

The server should send the schema signature so the client could compare it with their copy and refresh and re-parse the original server resposne (or not and merely report that the cache is out-of-date).


Metadata Update from @rcritten:
- Issue assigned to rcritten

2 years ago

master:

  • b842b82 Make the schema cache TTL user-configurable

ipa-4-9:

  • 331cadd Make the schema cache TTL user-configurable

Metadata Update from @frenaud:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Metadata Update from @rcritten:
- Custom field changelog adjusted to IPA clients store a copy of the server command schema, with a TTL of 1 hour by default. During plugin development command options, labels, etc may change and because some values are cached, new values will not display until the cache expires. This change adds a new configuration option, schema_ttl, so that a user can control how long the data is cached. A setting of 0 disables the cache. Tuning this is not recommended on production servers.

2 years ago

Metadata Update from @abbra:
- Issue tagged with: rfe

2 years ago

Login to comment on this ticket.

Metadata