fmaritato opened a new issue #18859:
URL: https://github.com/apache/superset/issues/18859
I am upgrading an existing superset 1.3.2 to 1.4.1 . I did not previously
have a SECRET_KEY defined. In reading the Updating.md file it says to set
PREVIOUS_SECRET_KEY but if I didnt have one set previously, what do I set this
to?
I tried PREVIOUS_SECRET_KEY = "" and ran `superset re-encrypt-secrets` but I
get an error:
```
superset.utils.encrypt:Collecting info for re encryption
Traceback (most recent call last):
File
"/usr/local/lib/python3.8/site-packages/sqlalchemy_utils/types/encrypted/encrypted_type.py",
line 128, in decrypt
decrypted = decrypted.decode('utf-8')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 1:
invalid start byte
```
I'm using a postgres database that has data in it that I can't lose, so I'm
stuck here. Any help would be appreciated.
Is there a specific table/row that I can manually delete to get past this?
### Environment
I'm using the apache/superset:1.4.1 docker image
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [ x ] I have checked the superset logs for python stacktraces and included
it here as text if there are any.
- [ x ] I have reproduced the issue with at least the latest released
version of superset.
- [ x ] I have checked the issue tracker for the same issue and I haven't
found one similar.
### Additional context
Add any other context about the problem here.
--
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]
