jtom38/fastapi_healthcheck

Easy to use health check for your FastAPI.

fastapi_healthcheck's Issues

tags should be optional

Right now, if tags are defined by a single tag, the module will not report on health and just throw an error. This needs to be updated so tags can be optional.

Add a license

Hi ! I would like to add fastapi_healthcheck to conda but I need a license file to do so. Could you add one ?
Thanks

Please support newer versions of FastAPI

I like the module, but unfortunately it only works with FastAPI 0.70-0.71 Would be nice when the latest versions are supported as well

Invalid models with Pydantic 2

Optional attributes in Models, like totalTimeTaken, should have a default value when used in some places like [self._health = HealthCheckModel()]https://github.com/jtom38/fastapi_healthcheck/blob/master/fastapi_healthcheck/service.py#L50, otherwise Pydantic 2 provides errors

Increase fastapi version range

I'd like to experiment with the package but I use the more recent version of [email protected]. When I try to add the package via poetry it emits the following error message:

$ poetry add fastapi-healthcheck
Using version ^0.2.8 for fastapi-healthcheck

Updating dependencies
Resolving dependencies...

Because fastapi-healthcheck (0.2.8) depends on fastapi (>=0.82.0,<0.83.0)
 and no versions of fastapi-healthcheck match >0.2.8,<0.3.0, fastapi-healthcheck (>=0.2.8,<0.3.0) requires fastapi (>=0.82.0,<0.83.0).
So, because spike-api depends on both fastapi (^0.88.0) and fastapi-healthcheck (^0.2.8), version solving failed.

Can you please adjust the fastapi version specifier to include larger version range?

Is there any reason to pinpoint fastapi dependency ?

Hi,

Is there any reason to pinpoint fastapi dependency in the package released on pypi ?

I understood you would like to validate it again when fastapi 1.0.0 is released, but, then, why not using

"fastapi < 1.0.0"

Into "pyproject.toml".

This way, you will get bug reports only if something is broken with some version of fastapi (until 1.0.0), because right now, you will have to release a new version of the package to bump the deps to follow exactly fastapi's versions.
(I mean, this "issue" could have been named "Please bump version", and then you will get a lot of those for each fastapi revision, even if nothing broke)
Maybe you want to ensure it is working for each fastapi version (and that's a valid reason, this "issue" is a real question)

The source of this is

 Because fastapi-healthcheck (0.2.7) depends on fastapi (>=0.82.0,<0.83.0)
   and youshinypackage depends on fastapi (^0.85.0), fastapi-healthcheck is forbidden.
  So, because firmware depends on fastapi-healthcheck (0.2.7), version solving failed.

Thanks a lot for your package !