Dump & Load User API Tokens

[JVickery-TBS]

Allows dumping and loading of user api tokens.

req: ckan/ckan#9339

cc: @wardi

[JVickery-TBS]

@wardi okay I think this makes more sense now. I also adding in a pop on the api_token_list so that it does not get sent to the user_update or user_create actions.

[JVickery-TBS]

Tests updated now too

[wardi]

A small test with mocked actions would be good to make sure this feature keeps working

[JVickery-TBS]

@wardi okay I have tests from dumping users, dumping users w/ api tokens, and loading users. I could not figure out coverage for loading users with tokens as the create api token action does model.User.get instead of user_show action so not sure how to mock that up

[JVickery-TBS]

@wardi okay I did the load api tokens test. And now log out the loaded tokens by name. Which I guess begs a new question, should I be handling the tokens that could not load and list them as skipped tokens? Like for ValidationErrors on token name already existing?

[wardi]

The way this is written multiple exceptions would be caught in the RemoteCKAN case but only NotFound will be caught in the LocalCKAN case, that's strange.

Suggested change

	except CKANAPIError:
	return
	except NotFound:
	return # with localckan we'll get the real CKAN exception not a CKANAPIError subclass
	except NotFound:
	return # with localckan we'll get the real CKAN exception not a CKANAPIError subclass

But, would we ever expect a NotFound? Won't that only happen if the user doesn't exist? If so it's better to not catch and ignore any exceptions.

[wardi]

But, I'll merge as-is and we can clean it up later.