Skip to content

Releases: python-microservices/pyms

v2.9.0rc1

25 May 19:12
Compare
Choose a tag to compare
v2.9.0rc1 Pre-release
Pre-release

Features

  • Replace pyenv in favor of poetry #237

Fixes

  • Update Pyms dependencies,
  • Fix issue "KeyError: 'WERKZEUG_SERVER_FD'" #241 (PR #246)
  • Fix issue "KeyError: 'APP_NAME'," #242 (PR #246)
  • Integrate last version of Connexion
  • Deprecate opentracing
  • Deprecate jaeger_client
  • Depreacte prometheus

v2.8.0

26 Jan 19:46
Compare
Choose a tag to compare

Features

  • Updated dependencies. anyconfig security risk #223
  • Support more parameters for Connexion #222
  • Support registration in Consul and created a driver to connect other Services Discovery #221
  • Added command create-config #204 - @path2himanshu

v2.7.0

23 Oct 18:37
Compare
Choose a tag to compare

Features

Improvements

v2.6.1

23 Sep 14:05
Compare
Choose a tag to compare

Fixes

v2.6.0

23 Apr 19:18
Compare
Choose a tag to compare

Features

  • Ability to use segmented API Specification (Swagger) included, ie, could have the following structure #115 - @f-arruza
    - components/
      - domain01/
        - responses.yaml
        - schemas.yaml
      - responses.yaml
      - schemas.yaml
    - info.yaml
    - servers.yaml
    - swagger.yaml **(main)**
    
  • Feature bundled specs command pyms merge-swagger #116 - @f-arruza

v2.5.1

18 Apr 10:07
Compare
Choose a tag to compare

Fixes

  • Fix init services in tests #114
    If you import config() from pyms.flask.app import config and initialize the config file inside a function like
@pytest.fixture
def app():
    """
    Return app for testing
    """
    base_dir = os.path.dirname(os.path.abspath(__file__))
    os.environ[CONFIGMAP_FILE_ENVIRONMENT] = os.path.join(base_dir, "config-test.yml")

The singleton pattern not reinitializes the services correctly

v2.5.0

12 Apr 15:43
Compare
Choose a tag to compare

Features

  • Reverse proxy pattern #103
  • Added AWS kms support #105
  • Added patch method to request service #104 - @LiangJQ

Fixes

  • Don't enable services implicitly #106
    When receiving a request, it will return the next error:
    Tracer error: 'NoneType' object has no attribute 'tracer'
    

v2.4.3

23 Mar 16:57
Compare
Choose a tag to compare

Fixes

  • Dependency error when not install py-ms with [all]. Raise this error:
Traceback:
[...]
from pyms.flask.app import config
../../.local/share/virtualenvs/lib/python3.7/site-packages/pyms/flask/app/__init__.py:1: in <module>
from .create_app import Microservice
../../.local/share/virtualenvs/lib/python3.7/site-packages/pyms/flask/app/create_app.py:6: in <module>
from flask_opentracing import FlaskTracing
ModuleNotFoundError: No module named 'flask_opentracing'```

v2.4.1

16 Mar 19:50
Compare
Choose a tag to compare

Fixes

  • Connexion path in OpenAPI 3.0
    In some case, with the last version of Connexion, doesn`t understand relative path to swagger. For example, f you use OpenAPI 3 in your swagger yaml file:
---
openapi: 3.0.2
info:
  title: Testing
  version: 1.0.0
  description: Testing
  termsOfService: http://swagger.io/terms/
  contact:
    name: Testing
    email: test@test.com
servers:
- url: http://localhost:8080/test/path/
  description: ""
paths:
  /test-url:

and in your configuration file APPLICATION_ROOT is defined like

  config:
    DEBUG: false
    TESTING: false
    APP_NAME: Films&Actors
    APPLICATION_ROOT : ""

The servers.url in swagger file override the base path of your application

v2.4.0

15 Mar 12:10
Compare
Choose a tag to compare

Features

  • Metrics fixes - @alexppg
    • Add http status code to latency metrics
    • Also, change some metrics and labels name to make them more standard.
  • Removed required param path in Microservice Class. Autodetect the current directory, If you want to deploy the microservice to production with gunicorn we recommended use path

Fixes

  • Connexion path
    In some case, with the last version of Connexion, doesn`t understand relative path to swagger