Helm Issue: additionalRequirements not working as expected

[kompetenzlandkarte]

I am trying to install superset on my kubernetes cluster. Hence I tried to install it via the helm chart. Also I want to use the vertica driver. So I specified the additionalRequirements property in the values.yml. Looking like this:

additionalRequirements:
  - sqlalchemy-vertica-python

#
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#    http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#

# Default values for superset.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates
...

Expected results

When I specify additionalRequirements the additional requirements get installed.

Actual results

When I add the connection string like:

vertica+vertica_python://...

I get the error: ERROR: Could not load database driver: VerticaEngineSpec

Screenshots

N/A

How to reproduce the bug

see above

Environment

(please complete the following information):

• superset version: Version: 0.999.0dev
• python version: v3.7.9
• node.js version: node -v

[kompetenzlandkarte]

Using the 1.1.0 Tag instead of latest solved the issue for me.

[Yann-J]

Just discovered this as well, it looks like this PR broke my deployment: #13917

The additionalRequirements was moved to a startup script in bootstrapScript...

[xasx]

This bug is still on master, thus in the latest version of the chart.

I propose reopening this issue.