A common use-case is having different HIT type properties for the live site versus the sandbox,
since test accounts on the sandbox often don't have high enough qualifications to work the HITs.
This feature would enable users to define, in their definition directories, separate HIT type
properties for the different amti environments.
An alternative feature that'd serve the same purpose would be to add a --quals/--no-quals flag. Thus, when posting to the sandbox, users could omit the quals if desired.
A common use-case is having different HIT type properties for the live site versus the sandbox, since test accounts on the sandbox often don't have high enough qualifications to work the HITs.
This feature would enable users to define, in their definition directories, separate HIT type properties for the different amti environments.