Custom environment URL schemas

Release notes

Problem to solve

Environment URLs are currently expected to be HTTP(S) URLs, but there are other kinds of "deployable" applications with their own schemas. For example, databases like Redis, MySQL and PostgreSQL. Having such URLs accepted would enrich the metadata of the deployment and could also be convenient for users with applications that can handle such URLs (e.g. a PostgreSQL database client that can open postgresql:// URLs).

Proposal

Either:

1. Allow arbitrary values in environment URL,
2. Or, extend support to well known schemas. Optionally, allow the user to specify the expected kind (useful for dynamically generated URLs), e.g.

   production:
     environment:
       name: production
       url:
         value: rediss://my-redis
         schema: redis
         strict: true # default false, but if true and value is invalid, then fail the job before it starts

Intended users

Feature Usage Metrics

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.