Correct, I didn't expect it to support puppet right now, since that is a separate task.  Since the controller has been named using a generic term ('content'), I was mostly curious if we've already determined that the APIs will be effectively the same regardless of content type (e.g. yum vs puppet).  We can revisit naming if we find later that the APIs are entirely different between content types.