Options to work-around #12696:
- Make the traceback more user friendly by linking to the GitLab issue.
- Catch the exception and assume the approved field is not present.
- Add a parameter for the user to specify whether the GitLab has the approved field or not and skip the GraphQL introspection query.
- Determine in some other way whether GitLab has the approved field, for example by checking the GitLab edition using
api/v4/version, see https://docs.gitlab.com/api/metadata/.
Let's try the last option. The version endpoint returns whether the GitLab instance is enterprise or not. Assume that enterprise editions have the approved field and non-enterprise editions do not.
Options to work-around #12696:
api/v4/version, see https://docs.gitlab.com/api/metadata/.Let's try the last option. The version endpoint returns whether the GitLab instance is enterprise or not. Assume that enterprise editions have the approved field and non-enterprise editions do not.