[BUG] - 'AWS_SECRET_ACCESS_KEY' requested on a digital ocean installation
See original GitHub issueOS system and architecture in which you are running QHub
ubuntu 20.04
Expected behavior
running
nebari init --guided-init and installing on DO
running on DO so iβve provided the following variables= SPACES_ACCESS_KEY_ID= β¦ SPACES_SECRET_ACCESS_KEY= β¦ DIGITALOCEAN_TOKEN= β¦
Actual behavior
hereβs the output
anaconda3/lib/python3.9/site-packages/nebari/utils.py:163 in check_cloud_credentials
so you can see that it knows itβs supposed to be pulling AWS info, but the variable must be getting requested somewhere?
β β β 'jupyterhub': { β β β β β β β 'hub_title': 'Nebari - nebari', β β β β β β β 'hub_subtitle': 'Your open source data science platform, hosted on β β β β Digital Ocean', β β β β β β β 'welcome': 'Welcome! Learn about Nebari\'s features and β β β β configurations in <a href="https://ww'+191, β β β β β β β 'logo': β β β β 'https://raw.githubusercontent.com/nebari-dev/nebari-design/main/logo-mark/horizβ¦ β β β β β β β 'display_version': True β β β β β β } β β β β β }, β β β β β 'helm_extensions': [], β β β β β 'monitoring': {'enabled': True}, β β β β β ... +10 β β β β } β β β β variable = 'AWS_SECRET_ACCESS_KEY'
How to Reproduce the problem?
run this on DO with guided init on an ubuntu 20.xx box
Command output
No response
Versions and dependencies used.
No response
Compute environment
No response
Integrations
No response
Anything else?
No response
Issue Analytics
- State:
- Created a year ago
- Comments:8 (5 by maintainers)
Closed by #1529
Hi @alibama this issue should have been fixed in the latest release
2022.11.1
, if youβre still running into trouble, please let us know π