Deploy Key without a user does not run PostReceive properly
Customer is using a writable Deploy Key to mirror changes from BitBucket to GitLab. They also have a similar setup from Gerrit. They created the Deploy Keys via the API, which apparently does not enforce that deploy keys have users.
Workaround is to associated the Deploy Key to a user via the Rails console.
The customer has concerns about simply enforcing the ownership of Deploy Keys across the GitLab instance. They often have people moving teams or leaving the company. And especially with widely used Deploy Keys they don't want one person leaving the team (blocked user) to halt every automated operation that uses that Deploy Key. They also want to avoid dealing with service accounts for a variety of reasons.
- How can we associated users with Deploy Keys for the purpose of attributing pushes, but still ease the pain when a person is no longer a GitLab user?
Original description below
Customer observes that when changes are pulled in from a BitBucket (on prem) mirror no activity is generated nor do web hooks fire. They do see the updates in the repository, though. We checked that
hooks/ are symlinked propertly and also observe that activity and web hooks are triggered normally when pushing directly to the repository.
I have tested this on both GitLab.com and on 10.3.4 local (that's the customer's version) against bitbucket.org and cannot reproduce. When the mirror pulls in updates I see activity and web hooks are triggered.