provincie-zuid-holland / omgevingsbeleid-api Goto Github PK

At the moment the user should have the test database prepared by itself. It would be nice if it is prepared automatically. This will make it easier for new users to use.

Dit omdat het verwachte rapport pas rond bekendmaking komt. En dat is te laat om bijvoorbeeld het programma naast de omgevingsvisie te publiceren.

We are adding a lot of python dependencies which are only needed in local dev and tests environment.
We could be splitting the requirements.txt file into a prod and dev specific file, in which the dev file includes the prod file and adds additional dev/test dependencies (like test tooling)

This way there will be less dependencies installed on the production environment.

Downside is that you no longer can use pip freeze to a requirements file because you have more then one.

See this link for an example configuration:
https://stackoverflow.com/questions/17803829/how-to-customize-a-requirements-txt-for-multiple-environments

When installing the requirements via pip install -r requirements.txt, the following error is raised:

ERROR: Cannot install -r requirements.txt (line 54) and urllib3==1.26.5 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested urllib3==1.26.5
    requests 2.24.0 depends on urllib3!=1.25.0, !=1.25.1, <1.26 and >=1.21.1

The API needs a database to fetch the asked for data. A description of which tables, columns and types are needed, would be welcome. This may be in the form of a sample database, or in the form of a ddl script

It seems possible to let views be managed by sqlalchemy. Having the views be managed by the same tool that managed the tables themselves will guard us from mistakes

We should take a look at what is possible.

Source:
https://sqlalchemy-utils.readthedocs.io/en/latest/view.html

Lifetime is a bit too high for my take, its 4 hours while 20 minutes seems the default.
To lower the lifetime we should add a refresh token which will refresh the lifetime when it gets "close" to expiration

• Moet eigenlijk alleen kunnen:
• • Voor de laatste state change versie
• • Wanneer die "package" nog niet bekend is
• Moet ook de state terug sturen waar nodig

cryptography==2.9.2 and lxml==4.5.2 do not install when python 3.9 is used.