[GT-184] Add support for renewing API credentials - #464
Conversation
5728cd9 to
6f26459
Compare
bc37f58 to
6259cc5
Compare
8afb986 to
cd82c9e
Compare
|
@gregcorbett , This is ready for the functionality review. |
gregcorbett
left a comment
There was a problem hiding this comment.
Functionality looks good. I noticed that when emails were generated for both unrenewed and inactive API credentitals, I got:
> php resources/ManageAPICredentials/ManageUnusedAPICredentials.php --warning_threshold 9 --deletion_threshold 15 --renewals
...
The API credential associated with the following identifier
registered at site X has not been renewed for
the last 0 months and will be deleted if it reaches 15 months.
Where 0 should have been closer to 12, which is why the warning email was generated. Could you look into that?
|
Could you also add printing out the last renewed time to |
Sure, Greg. Added the support for last renewed time in 0d1ec9a |
|
Ready for the functionality review with the fix and suggestions @gregcorbett. |
61d1865 to
0577fbc
Compare
|
@Sae126V , can you remember why Was it to support being able to renew (and hence take ownership of, if necessary) a credential without otherwise editing it (i.e. a renew button in the portal)? If so, I wonder if there is a version of this change that doesn't touch |
Yep, so, it was changed to support the renew button. The problem is that a renewal doesn't send any form fields (the point of "renew without otherwise editing it"), but the existing I'll investigate whether there's a version that doesn't touch this file and get back to you by tomorrow |
Presumably we could just send the current values into |
a7d8e3d to
e123f64
Compare
|
I have changed the logic of renewal flow. This would be now separate from the editing user flow. Ready for the review now |
e058dda to
00858bd
Compare
00858bd to
491abeb
Compare
7d74c41 to
c5179f1
Compare
Resolves
" #438 and #453 "