Skip to content

Pass namespace in the params

What does this MR do and why?

Currently, the (/trials/new) process is:

  1. In GitLab after selecting or creating a group, trigger a trial on CustomersDot
  2. On CustomersDot, ask GitLab(via api call) some things about the namespace - 'id', 'name', 'path', 'kind', 'trial_ends_on'.
  3. Create the trial on CustomersDot
  4. Respond to initial Post from GitLab.
  5. Update the namespace on GitLab with an admin token from CustomersDot in the background

Sometimes we are seeing step #2 fail due to token expiration or other reasons.

Solution

We could likely send the info that customersDot needs from #2 in the initial payload from GitLab in #1 and forgo asking GitLab for it again in #2.

How to set up and validate locally

https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/7180#how-to-set-up-and-validate-locally

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #403054 (closed)

Edited by Doug Stull

Merge request reports

Loading