Adapt SubscriptionDetails for purchasing the CI Minutes addon
What does this MR do?
This is the 1st merge request that adapts the SubscriptionDetails component for
purchasing an addon (CI Minutes or Storage pack). Right now the component has hardcoded
values for CI Minutes pack, later we will change them to dynamic string that depend on the picked addon.
Next steps will be adapt all other components in the purchase flow and generalize this workflow for purchasing any addon.
See this epic for more information.
How to test this locally
-
Make sure you have the CustomersDot app running locally.
-
Make sure your local GDK instance points to your local CustomersDot. You the following lines to the
env.runitfile in the root folder of your GDK installation:export CUSTOMER_PORTAL_URL=http://localhost:5000/ -
Enable the following feature flag
Feature.enable(:new_route_ci_minutes_purchase) -
Sign in into your local GitLab instance and navigate to
-/subscriptions/buy_minutes
Screenshots (strongly suggested)
| Description | Image |
|---|---|
| Entering quantity |  |
After clicked on Continue to billing
|
 |
ci_minutes_purchase-2021-07-02_09.12.53
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team