I guess I'm looking for clarification here on how these things are related (if at all) and what the implications may be of treating one as the other. At a more basic level, clarification on what Drydock resource types represent in general would be helpful.
It's fairly clear via APIs and existing implementations what the intentions are for harbormaster artifact types.
I'm referring specifically to the string constant that the artifacts and blueprints each define. There is some indication that these constants are not interchangeable, specifically in [[ https://secure.phabricator.com/diffusion/P/browse/master/src/applications/harbormaster/step/HarbormasterLeaseWorkingCopyBuildStepImplementation.php;c7e7f113fd97389661a74ae0f27c443ce8622ba6$41 | HarbormasterLeaseWorkingCopyBuildStepImplementation ]], the constant for the resource is pulled from the resource blueprint, and the constant representing the artifact type is referenced using the class constant.