Privately hosted templates are not supported

[djejaquino]

🐛 Bug report

Current Behavior

Running a npx @availity/worflow init command with -t or --template parameter, using a privately hosted starter will abort the process.

Expected behavior

To successfully initialize an updated workflow-based project.

Reproducible example

Suggested solution(s)

Assume static hostedInfo for https://code.availity.com, to support (at least) Availity-provided repositories.

Additional context

availity-workflow/packages/workflow/scripts/clone-starter.js

Line 64 in 12c486b

Logger.failed('Could not find Hosted Git Info for the Project.', hostedInfo);

Your environment

  Binaries:
    Node: 8.9.4 - C:\Program Files\IBM\node\node.EXE
    Yarn: 1.22.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 5.6.0 - C:\Program Files\IBM\node\npm.CMD

EDIT: grammar

[nylon22]

Some background on this. We use a library: https://github.com/npm/hosted-git-info, to get metadata about the git url passed in via the template option before cloning it. You can see that here:

availity-workflow/packages/workflow/scripts/clone-starter.js

Lines 59 to 65 in 2e57fc9

	const hostedInfo = hostedGitInfo.fromUrl(templateUrl);
	if (hostedInfo) {
	await clone(hostedInfo, appPath);
	} else {
	Logger.failed('Could not find Hosted Git Info for the Project.', hostedInfo);
	}

That library does not support https://code.availity.com. I see two paths forward here:

1. The library does support pull requests for new hosts. We could add this host.
2. We can remove the dependency on that library and do what it does in-house.

[nylon22]

Related: npm/hosted-git-info#39