Known Issue [Resolved]: Using the Liferay PaaS CLI lcp deploy command removes the git origin configuration

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

• After using the lcp deploy command in the CLI to deploy a service, the command seems to erase the existing git remote origin configurations, replacing it with a blank value (observed when executing the git remote -v command). Though the lcp deploy  itself is successful, it then causes the following error when attempting to push another build to the repository:

  fatal: 'origin' does not appear to be a git repository
  fatal: Could not read from remote repository.
  
  Please make sure you have the correct access rights
  and the repository exists.

• Attempting to update from CLI version 3.7.8 to 3.7.9 or 3.8.0 does not appear to resolve the issue.

Environment

• Liferay PaaS CLI

Resolution

• This behavior can be resolved by updating the CLI to v3.8.1+, using lcp update, which will prevent lcp deploy from erasing the git origin value

Additional Information

• If the git origin was previously erased, the following commands can be executed in a terminal to restore the missing git origin value (this only needs to be executed once after updating to v3.8.1):
  

  git remote remove origin
  git remote add origin [origin value; for example, [e-mail]:organization/repository.git]

• Deploying Changes via the CLI Tool
• How to update and deploy only a single service with Liferay PaaS