Treat environments matching `production/*` as Production for Cycle Analytics
What does this MR do?
For Cycle Analytics, the environment production
is treated as a
special case, and used to update the first_deployed_to_production_at
metric.
With the Review Apps changes, slash syntax is used to group related
environments in the list. This is mostly used for review/<branch>
environments, but it's possible for people to have multiple production
environments, and someone might then want to group them like
production/eu
, production/us
, or even just make it look prettier
with production/www.example.com
. In any of these cases, the first
deploy to one of these production/*
environments now is treated as a
Production deploy.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #24139 (closed)