All Versions
74
Latest Version
Avg Release Cycle
137 days
Latest Release
1726 days ago

Changelog History
Page 1

  • v3.0.0 Changes

    July 26, 2019
    • 🛠 Fix issue where config could not be read at service import time (#651 )

  • v3.0.0-rc9 Changes

    October 10, 2020
    • ✂ Remove or ignore a bunch of deprecation warnings in the test suite
    • ➕ Add timeout parameter to entrypoint_hook (#622)
    • 👌 Support for Python 3.7 (#644)
    • 🛠 Fix Python 3.7 warning on collections.abc (#649)
    • ➕ Add --version flag to CLI tool (#663)
    • ✂ Remove support for Python 3.4 and support Werkzeug>1 (#680)

  • v3.0.0-rc8 Changes

    July 26, 2019
    • 🛠 Fix issue where config could not be read at service import time (#651 )

  • v3.0.0-rc7 Changes

    June 27, 2019
    • 🚚 CLI improvements (#620, #618, #623, #625 - nameko backdoor removed)
    • 🛠 Fix default AMQP_URI

  • v3.0.0-rc6 Changes

    March 19, 2019
    • Test helpers container_factory and runner_factory now take custom config argument (as they used to in Nameko 2.X). Config patch is applied if a config dictionary is passed to these factories. (#610)
    • CLI got new -c alternative to --config option (#605)
    • 🔨 Refactor utils so standalone.events does not import eventlet (#580)
    • ✅ Compatibility with latest dependencies (moto #577, pyyaml and kombu #612)
    • Timer now waits for the spawned entrypoint to complete before firing again, as documented (#579, #303)
    • Timer is also improved to avoid drift (#614)
    • Hide password in logged amqp uri (#582)
    • 📄 Docs updates (#587, #591, #276, #596)
    • Nameko shell changed to not catch exceptions when used in non-TTY mode (#597)

  • v3.0.0-rc5 Changes

    January 14, 2019
    • 👍 Better config API helpers

    ✅ A small tweak to the new config API introduced in rc4. Improves the naming and adds a decorator interface for simpler, more explicit use in tests.

  • v3.0.0-rc4 Changes

    January 11, 2019
    • Set extra headers for outbound messaging as late as possible

    ➕ Addresses a limitation whereby context data changed during method execution was not propagated to downstream services.

  • v3.0.0-rc3 Changes

    January 05, 2019
    • 🔧 Configuration loaded from a file or declared in the CLI is now available in a global object.

    Example:

    from nameko.messaging import Consumerfrom nameko import configclass Service: @consume( queue=Queue( exchange=config["MY\_EXCHANGE"], routing\_key=config["MY\_ROUTING\_KEY"], name=config["MY\_QUEUE\_NAME"] ), prefetch\_count=config["MY\_CONSUMER\_PREFETCH\_COUNT"] ) def consume(self, payload): pass

    • 🔧 Configuration may now be declared on the CLI:

      $ nameko run service \ --define AMQP_URI=pyamqp://user:pass@host/vhost \ --define MY_EXCHANGE="exchange" \ --define MY_ROUTING_KEY="route" \ --define MY_QUEUE_NAME="queue" \ --define MY_PREFETCH_COUNT=100 \

    • 🔧 Configuration access via the service container is now deprecated.

    • 🔧 Builtin extensions and other facilities that read the configuration now access it via the global

  • v3.0.0-rc2 Changes

    November 22, 2018

    🛠 Fixes minor issues discovered during pre-release testing:

    • Missing backwards compatibility shim from ClusterRpcProxy and ServiceRpcProxy in nameko.standalone.rpc
    • EventHandler and Consumer entrypoints could not accept expected_exceptions or sensitive_arguments keywords.

  • v3.0.0-rc1 Changes

    November 19, 2018

    ➕ Adds a ClusterRpc DependencyProvider, allowing services to make RPC calls without prior knowledge of the target service name.

    ➕ Additonally removes the word "proxy" from RPC clients:

    • standalone ServiceRpcProxy renamed to ServiceRpcClient
    • standalone ClusterRpcProxy renamed to ClusterRpcClient
    • DependencyProvider ServiceRpcProxy renamed to ServiceRpc
    • (DependencyProvider ClusterRpc added)

    The old names have been preserved for backwards compatibility.