Credentials template for better reuse

[vaclavdobsicek]

This way of initialize the credentials file covers also the scenario, when the already initialized repo is pulled to the new location.

In this case the credentials.json file is not pulled (because it does not exists on the remote) and it is needed to look into documentation, how this file should looks like and what structure it have.

This problem is solved using template version credentials.template.json which is not ignored and is present also in remote.

[rehoumir]

@vaclavdobsicek , I likely don't understand the issue this is solving - the usual workflow is:

1. Run prd initialize <project-name>
2. Fill in the credentials in credentials.json (this file is created by initialize already, no?)
3. Run prd pull

When you say "already initialized repo", how did you initialize it if not via prd initialize?

[vaclavdobsicek]

By calling git clone of already initialized project stored in some git repo.

[rehoumir]

I see, thanks. And what would happen if you ran git clone followed by prd initialize? Won't that create the credentials.json file already now?

[vaclavdobsicek]

@rehoumir Honestly, IDK :-) Will it create the credentials.json file?

Btw. to run "initialize" command inside an already-created environment is unusual, IMO.

[rehoumir]

@vaclavdobsicek , it does. I will close this PR therefore.

[rehoumir]

@vaclavdobsicek , "Odvolávám, co jsem odvolal". :D I tried to do it the "current way" and there are at least 3 extra commands. Your solution is better. :)