feature/check-for-expired-or-soon-to-be-expired-key

[bwalsh]

With an expired key:
A user can currently run through the entire workflow including adding files, committing them and pushing to the server - and never be informed of an expired key.

Suggested improvements:

• Check for expired key, if expired raise informative error (ie a link to documentation )
• Check for threshold days expiration, raise warning
  Do this at:
• git drs add remote
• git push
• git drs ls remote

See calypr admin

• https://github.com/calypr/admin/blob/development/calypr_admin/config/__init__.py#L57-L72
• https://github.com/calypr/admin/blob/development/calypr_admin/config/__init__.py#L150-L159

[jordan2lee]

This would be helpful to have. As a tester, I encountered the issue that some git drs commands would fail, but lack informative output messages.

Adding the suggested days expiration warning for those 3 commands would be perfect. Adding this message also forgit lfs track should be considered too (knowing from the first step that credentials will soon expire would be helpful)

[jordan2lee]

would it be possible to increase to 90 days the credential expiration? not a requirement, but would improve the user experience

[matthewpeterkort]

addressed in #232.