jamesrusso opened a new issue, #35843:
URL: https://github.com/apache/superset/issues/35843

   ### Bug description
   
   Specifying SUPERSET_LOAD_EXAMPLES=no in .env.local is ignored since the 
environment variable in the superset-init service in docker compose yaml file 
overrides this value.
   
   ```
     superset-init:
       image: *superset-image
       container_name: superset_init
       command: ["/app/docker/docker-init.sh"]
       env_file:
         - path: docker/.env # default
           required: true
         - path: docker/.env-local # optional override
           required: false
       depends_on:
         db:
           condition: service_started
         redis:
           condition: service_started
       user: "root"
       volumes: *superset-volumes
       healthcheck:
         disable: true
       environment:
         SUPERSET_LOAD_EXAMPLES: "${SUPERSET_LOAD_EXAMPLES:-yes}"
         SUPERSET_LOG_LEVEL: "${SUPERSET_LOG_LEVEL:-info}"
   ```
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   5.0.0
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [ ] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [ ] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [ ] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to