#6692 Exports should be scriptable; Simple oauth API via bearer tokens

v1.1.0
closed
Cory Johns
export (9) sf-2 (994)
General
Dave Brondsema
2015-08-20
2013-09-20
Dave Brondsema
No

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.

Related

Tickets: #4633

Discussion

<< < 1 2 (Page 2 of 2)

  • Dave Brondsema

    Dave Brondsema - 2013-10-25

    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.

     

  • Dave Brondsema

    Dave Brondsema - 2013-10-25
    • status: code-review --> in-progress
     

  • Cory Johns - 2013-10-29
    • status: in-progress --> code-review
     

  • Cory Johns - 2013-10-29

    Example script and new tests force-pushed to:
    allura:cj/6692

    Other branches unchanged:
    forge-classic:cj/6692
    sfx:cj/6692

     

  • Cory Johns - 2013-10-31

    Bash version of export script pushed to:
    allura:cj/6692

     

  • Dave Brondsema

    Dave Brondsema - 2013-10-31
    • status: code-review --> closed
     
<< < 1 2 (Page 2 of 2)

Log in to post a comment.