Uninstall fails critically if there is no configured graphql server

Created on 7 October 2022, about 2 years ago
Updated 17 October 2023, about 1 year ago

Problem/Motivation

When importing config in non-configured environments where we cannot or don't want to authenticate with the product server, we set in the splits not to install perz or its dependencies. When the Perz module tries to uninstall itself from the prod database, it looks for a configured Graphql server to remove, when it doesn't find one it fails critically.

Steps to reproduce

install perz with dependencies on a database, set splits on a branch to remove the dependencies, run an import on the installed database with the split.

Proposed resolution

Put an if check around the check for a graphql server

πŸ› Bug report
Status

Closed: won't fix

Version

4.1

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States DrupalHack

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024