can't change secret key

[PNA921]

Hi!
I'm trying to change default secret key in my Superset 1.5.1. according to the instructions from superset web site.
When I log into the container and enter the command "superset shell" I get an error:
root@0c5b24f8ad75:/app# superset shell
Traceback (most recent call last):
File "/usr/local/bin/superset", line 33, in
sys.exit(load_entry_point('apache-superset', 'console_scripts', 'superset')())
File "/usr/local/bin/superset", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/local/lib/python3.8/importlib/metadata.py", line 79, in load
return functools.reduce(getattr, attrs, module)
AttributeError: module 'superset.cli' has no attribute 'superset'

And I can't enter any other command, like "superset --versiont". I get same error.
What I can do with it?

[dosubot[bot]]

Hello @PNA921! 👋 I'm here to help you with any issues or questions you have. I'm a bot designed to assist with bug fixes, answer questions, and guide you on becoming a contributor.

To resolve the AttributeError when trying to run superset shell or any other superset command in Superset 1.5.1, ensure that the superset function is properly defined and that the @with_appcontext decorator is correctly applied. Here is the relevant part of the code that defines the superset CLI group and adds sub-commands:

@click.group(
    cls=FlaskGroup,
    context_settings={"token_normalize_func": normalize_token},
)
@with_appcontext
def superset() -> None:
    """\033[1;37mThe Apache Superset CLI\033[0m"""
    # NOTE: codes above are ANSI color codes for bold white in CLI header ^^^

    @app.shell_context_processor
    def make_shell_context() -> dict[str, Any]:
        return {"app": app, "db": db}

# add sub-commands
for load, module_name, is_pkg in pkgutil.walk_packages(
    cli.__path__, cli.__name__ + "."
):
    module = importlib.import_module(module_name)
    for attribute in module.__dict__.values():
        if isinstance(attribute, (click.core.Command, click.core.Group)):
            superset.add_command(attribute)

            if isinstance(attribute, click.core.Group):
                break

Additionally, in versions after 1.5.1, all Superset CLI commands now require setting the FLASK_APP environment variable. You can set this variable by running:

export FLASK_APP=superset

This change ensures that the necessary environment variable is set, which could prevent the AttributeError related to missing configurations or context ^[1][2].

If the issue persists, it might be due to an environment-specific problem or a missing dependency. Double-check your environment setup and ensure all necessary packages are installed.

To continue talking to Dosu, mention @dosu.

[PNA921]

Thank you!
For @dosu
I found out that the line was spelled incorrectly in file entry_points.txt
cat /app/apache_superset.egg-info/entry_points.txt
[console_scripts]
superset = superset.cli:superset

I need to change it, to string:
superset = superset.cli.main:superset
Where I can change it , so that the settings are not reset for the new container superset_app.
Сhanging the file "setup.py" does not help

[dosubot[bot]]

To ensure that the settings are not reset for the new container superset_app, you need to modify the entry_points.txt file in a way that persists across container restarts. Here’s how you can do it:

1. Create a Custom Dockerfile: Create a custom Dockerfile that modifies the entry_points.txt file.

2. Modify the docker-compose-non-dev.yml: Update the docker-compose-non-dev.yml to use your custom Dockerfile.

Here’s a step-by-step guide:

Step 1: Create a Custom Dockerfile

Create a new Dockerfile, for example, Dockerfile.custom:

FROM apache/superset:latest

# Copy the modified entry_points.txt into the container
COPY entry_points.txt /app/apache_superset.egg-info/entry_points.txt

Step 2: Create the Modified entry_points.txt

Create a new entry_points.txt file with the corrected entry point:

[console_scripts]
superset = superset.cli.main:superset

Step 3: Update docker-compose-non-dev.yml

Modify the docker-compose-non-dev.yml to use your custom Dockerfile:

  superset:
    env_file:
      - path: docker/.env # default
        required: true
      - path: docker/.env-local # optional override
        required: false
    build:
      context: .
      dockerfile: Dockerfile.custom
    container_name: superset_app
    command: ["/app/docker/docker-bootstrap.sh", "app-gunicorn"]
    user: "root"
    restart: unless-stopped
    ports:
      - 8088:8088
    depends_on: *superset-depends-on
    volumes: *superset-volumes

Step 4: Rebuild and Restart the Container

Rebuild the Docker image and restart the container:

docker-compose -f docker-compose-non-dev.yml build
docker-compose -f docker-compose-non-dev.yml up -d

This approach ensures that your changes to entry_points.txt are included in the Docker image and persist across container restarts ^[1].

To continue talking to Dosu, mention @dosu.