Check the bulk-user-load CSV dictreader's headers instead of feeding the headers to the CSV dict reader; this prevents the header-as-data problem and we may get a more explicit error message. We also have the option of doing a set-wise comparison if we want to allow headers to be in any order.
Additionally we prompt webapi to init the sec_* table entries for each new account by logging in with the new credentials.
actualben
commented
4 months ago
Check the bulk-user-load CSV dictreader's headers instead of feeding the headers to the CSV dict reader; this prevents the header-as-data problem and we may get a more explicit error message. We also have the option of doing a set-wise comparison if we want to allow headers to be in any order.
Additionally we prompt webapi to init the sec_* table entries for each new account by logging in with the new credentials.