Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
customers-gitlab-com
customers-gitlab-com
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 574
    • Issues 574
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards
  • GitLab.org
  • customers-gitlab-comcustomers-gitlab-com
  • Issues
  • #1222

Closed
Open
Opened Mar 27, 2020 by Jackie Fraser@jackie_fraser🔴Developer

Namespace api updates for customers that don't have a valid access_token

The change made in this MR removed the Admin token for GitLab api updates, switching to the customer's access token.

However TrialsController#create started failing because those customers do not have an access token.

https://sentry.gitlab.net/gitlab/customersgitlabcom/issues/1436534/?query=is%3Aunresolved

There is also an issue with the Zuora Callback controller, in some cases it creates a brand new customer in some cases here: https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/staging/app/controllers/zuora_callbacks_controller.rb#L25 - this will need to be investigated as to how to get a valid access_token for them.

The MR was reverted for now to sort out the above two namespace API updates.

Problem

Proposal

Result

Next steps (if any)

Figure out if we can sync these customers at GitLab without the Admin token.

How will we measure success?

Assignee
Assign to
13.0
Milestone
13.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/customers-gitlab-com#1222