All Collections
Using Salto
Documenting Changes
Git
Our Consultant Cannot PUSH Changes to Our Repository
Our Consultant Cannot PUSH Changes to Our Repository

An organization with an environment linked to a repository. PUSH works for our staff but fails for our consultant's staff.

Zalary Young avatar
Written by Zalary Young
Updated over a week ago

Scenario

  1. An organization (acme.com) with a Salto environment successfully linked to a GitHub repository

  2. A consultant from an outside company (coyote.com) is a valid Salto admin in the organization

  3. The consultant performs a deployment and wishes to PUSH the changes to the organization's GitHub repository.

  4. The PUSH fails (with an internal server error)

Known Issue

While the Github repository is owned and administered by the organization, it may be configured such that only staff members of the organization have read/write access to the repository and its branches.

The consultant with e-mail address in the consultant's domain (coyote.com), by default, is not configured as a collaborator in the repository and, hence, the consultant's PUSH operations will fail (and trigger an INCIDENT alert in the Salto monitoring system).

Solution

The GitHub administrator for the organization (acme.com) should be sure to add the consultant as a collaborator in the organization's GitHub repository in GitHub as in the following example:

This will send an invitation to the consultant to join the repository as a valid collaborator.

After the consultant accepts the invitation, the consultant will be able to successfully PUSH changes from the Salto environment as if the consultant were one of the members of the organizations's staff.

Did this answer your question?