#5366 allura_import validation doesn't appear to work as documented
Originally created by: jpschewe
Per http://allura.sourceforge.net/migration.html#validating-import-data I tried running allura_import.py to check my import data. It seems that an api key may be required even for validation. Is this expected?
Here is my command execution and trace. This is with the fixes for ticket 5364 and 5364 applied.
jpschewe@jon:~/src/allura-git
[git:ticket-] >python scripts/allura_import.py -a api-key -s secret-key -u https://sourceforge.net -p test -t bugs --user-map=/home/jpschewe/projects/fll-sw/user_map.json --validate /home/jpschewe/projects/fll-sw/allura-import.json churchid churchid
jschewe jpschewe
jvriezen jvriezen
jjkoletar jjkoletar
nicolaslindgren nicolaslindgren
jpschewe jpschewe
eengstrom eengstrom
Traceback (most recent call last):
File "scripts/allura_import.py", line 126, in <module>
main()
File "scripts/allura_import.py", line 54, in main
verbose=options.verbose)
File "scripts/allura_import.py", line 83, in import_tracker
res = cli.call(url, doc=json.dumps(doc), options=json.dumps(import_options))
File "scripts/../Allura/allura/lib/import_api.py", line 44, in call
raise e
urllib2.HTTPError: HTTP Error 403: Forbidden