Test changes look great. As far as coverage goes, I think /auth/oauth/ is covered well, as are bearer tokens. I do think we should add coverage for consumer token usage (even though we've been missing that for a while - now's a good time to add it)
I was actually thinking of an example script for the backup API (remember what this ticket's about? ;) ) And API docs at https://sourceforge.net/p/forge/documentation/Allura%20API/ If the export script is simple enough (shell script even?) it could live on that public doc page. --- ** [tickets:#6692] Exports should be scriptable; Simple oauth API via bearer tokens** **Status:** code-review **Labels:** export **Created:** Fri Sep 20, 2013 05:43 PM UTC by Dave Brondsema **Last Updated:** Tue Oct 22, 2013 08:33 PM UTC **Owner:** Cory Johns Currently difficulties in project exports are: * requires a manual form submission * email is used to notify when ready * resulting filename is non-deterministic It should be possible to automate a project export with a script, with minimal difficulty. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
