Clearly state in the documentation which GitLab edition is required to use a specific feature
Description
We now have EE documentation by default on docs.gitlab.com, but sometimes it could be misleading for users that are not fully aware about our different editions.
For example (see https://gitlab.com/gitlab-org/gitlab-ce/issues/40326), users can try to access a specific ~"EE Premium" feature and get errors that are difficult to address because they are generic. Also, looking at the documentation, you find everything as you did, because documentation is for EE.
It is true that you can see it looking at the note:
The use of CI_JOB_TOKEN in the artifacts download API was introduced in GitLab Enterprise Edition Premium 9.5.
but I can also understand that may be lost.
Proposal
Make more explicit for EE which is the edition required for a specific feature, every time we mention it.
This will allow also to unify documentation between CE and EE.
Example:
Using the JOB-TOKEN header (only inside .gitlab-ci.yml):
Will be
Using the JOB-TOKEN header (only inside .gitlab-ci.yml): ~"EE Premium"
Links / references
Documentation blurb
Overview
What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?
Use cases
Who is this for? Provide one or more use cases.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml