FYI, I have rebased versions of all of these I can push.
The docstring on `ImportIdConverter` needs to be updated.
`ImportIdConverter` doesn't know what type of artifact it's converting. Does
that need to be accounted for yet? Or wait until we have a non-ticket
implementation, so we know how exactly it would work.
`ForgeTracker/forgetracker/tracker_main.py` assumes
`ImportIdConverter.get().expand` will return a dict, but it could return a
string, which will then error. And when it's a dict, querying by
`import_id.foobar` will be unindexed. There is an existing index on
`import_id` for a simple string match. I think an easy win is to just query
`{"import_id": expand_result}` it'll work with strings & dicts, and querying
against a full dict value will use the index that's on `import_id`
In the audit log, the URL value ends up being like
`/--forgeimporters.base.import_tool--/5228fa9cd8be3540e721915f//--forgeimporters.base.import_tool--/5228fa9cd8be3540e721915f/`
That's not ideal, but not too big of a deal either. The URL is set up by the
taskd runner (not sure why it's duplicated), so we'd have to override it
---
** [tickets:#6541] Record import_id and audit log during imports**
**Status:** in-progress
**Labels:** import
**Created:** Thu Aug 08, 2013 09:17 PM UTC by Dave Brondsema
**Last Updated:** Thu Sep 05, 2013 07:38 PM UTC
**Owner:** Cory Johns
We should keep track of the original source in imported artifacts. The
import_id field is just right for that. IIRC, tool configs may have an
import_id too. Both would be useful so that we could run reports on how my
tickets or trackers (for example) have been imported from elsewhere.
Also record each import in the project audit log.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org 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.
