PYTHON-ZAQARCLIENT(1)

📦
version 4.7.0 · 2 versions
, in nixpkgs unstable

✨ python-zaqarclient — PYTHON-ZAQARCLIENT(1) ✨

okay bestie, you opened the manual page for python-zaqarclient and honestly? iconic. This is the 4.7.0 era of the client, and we're gonna walk through it together like we're sharing earbuds on the bus. 🎧🦋

🌸 NAME 🌸

python-zaqarclient — python-zaqarclient 4.7.0

Zaqar (https://wiki.openstack.org/wiki/Zaqar) is a multi-tenant cloud messaging and notification service for web and mobile developers. 💖

The service features a ReST API, which developers can use to send messages between various components of their SaaS and mobile applications, by using a variety of communication patterns. Underlying this API is an efficient messaging engine designed with scalability and security in mind. no cap, that's the whole vibe. 🔥

Other OpenStack components can integrate with Zaqar to surface events to end users and to communicate with guest agents that run in the "over-cloud" layer.

Note: This documentation is generated by the Sphinx toolkit and lives in the Zaqar project source tree. Additional draft and project documentation regarding Zaqar and other components of OpenStack can be found on the OpenStack Wiki (https://wiki.openstack.org/wiki/Main_Page), as well as in the user guides found on docs.openstack.org (https://docs.openstack.org). 🫶

📚 CONTENTS 📚

  • Client
  • Client Object Reference
  • Command-line
  • Queue

🧸 Client 🧸

A Client is a high-level abstraction on top of Zaqar features. It exposes the server features with an object-oriented interface, which encourages dot notation and automatic, but lazy, resources allocation. A Client allows you to control everything, from public interfaces to admin endpoints. 💅

To create a Client instance, you supply an url pointing to the server and a version number:

from zaqarclient.queues import client

cli = client.Client('http://zaqar.example.com:8888/', version=2)

which will load the appropriate client based on the specified version. Optionally, you can also supply a config dictionary:

from zaqarclient.queues import client

cli = client.Client('http://zaqar.example.com:8888/',
                    version=2, conf={})

The arguments passed to this function will be passed to the client instances as well.

It's recommended to use Client instances instead of accessing the lower level API as it has been designed to ease the interaction with the server and it gives enough control for the most common cases. like, she's literally built for this. 👑

A simple example for accessing an existing queue through a client instance - based on the API v2 - would look like:

from zaqarclient.queues import client

cli = client.Client('http://zaqar.example.com:8888/', version=2)
queue = cli.queue('my_queue')

Through the queue instance will be then possible to access all the features associated with the queue itself like posting messages, getting message and deleting messages. 🎀

As mentioned previously in this documentation, a client instance allows you to also access admin endpoints, for example:

from zaqarclient.queues import client

cli = client.Client('http://zaqar.example.com:8888/', version=2)
flavor = cli.flavor('tasty',
                    pool='my-pool-group',
                    auto_create=True)
flavor.delete()

Client uses the lower-level API to access the server, which means anything you can do with this client instance can be done by accessing the underlying API, although not recommended. 🙈

📖 Client Object Reference 📖

This is the reference documentation for all API version. yes, all of it, bestie. 🌈

🌟 API v2.0 🌟

class Client(url=None, version=2, conf=None, session=None)

Client base class

  • Parameters
    • url (str) — Zaqar's instance base url.
    • version (int) — API Version pointing to.
    • conf (oslo_config.cfg.CONF) — CONF object.
  • flavor(ref, **kwargs) — Returns a flavor instance.
    • Parameters: ref (str) — Flavor's reference name.
    • Returns: A flavor instance.
    • Return type: flavor.Flavor
  • flavors(**params) — Gets a list of flavors from the server.
    • Parameters: params (dict.) — Filters to use for getting flavors.
    • Returns: A list of flavors.
    • Return type: list
  • follow(ref) — Follows ref. This method instanciates a new request instance and requests ref. It is intended to be used to follow a reference href gotten from links sections in responses like queues' lists.
    • Params ref: The reference path.
  • health() — Gets the detailed health status of Zaqar server.
  • homedoc() — Get the detailed resource doc of Zaqar server.
  • ping() — Gets the health status of Zaqar server.
  • pool(ref, **kwargs) — Returns a pool instance.
    • Parameters: ref (str) — Pool's reference name.
    • Returns: A pool instance.
    • Return type: pool.Pool
  • pools(**params) — Gets a list of pools from the server.
    • Parameters: params (dict.) — Filters to use for getting pools.
    • Returns: A list of pools.
    • Return type: list
  • queue(ref, **kwargs) — Returns a queue instance.
    • Parameters: ref (str) — Queue's reference id.
    • Returns: A queue instance.
    • Return type: queues.Queue
  • queues(**params) — Gets a list of queues from the server.
    • Returns: A list of queues.
    • Return type: list
  • subscription(queue_name, **kwargs) — Returns a subscription instance.
    • Parameters: queue_name (str) — Name of the queue to subscribe to.
    • Returns: A subscription instance.
    • Return type: subscription.Subscription
  • subscriptions(queue_name, **params) — Gets a list of subscriptions from the server.
    • Parameters: params (dict.) — Filters to use for getting subscriptions.
    • Returns: A list of subscriptions.
    • Return type: list
  • transport() — Gets a transport based the api url and version.
    • Return type: zaqarclient.transport.base.Transport

🖥️ Command-line 🖥️

This chapter documents the usage of Zaqar Client Command Line with API v2.0.

Zaqar client now support some kinds of resources or actions: queue, message, claim, subscription, pool, flavor, ping, health.

Click the Link below for the details. 🫶

👑 Queue 👑

For help on a specific openstack messaging queue command, enter:

$ openstack messaging queue COMMAND -h/--help

The fourteen commands:

messaging queue create
messaging queue delete
messaging queue get metadata
messaging queue list
messaging queue set metadata
messaging queue signed url
messaging queue stats

🛠️ openstack messaging queue create 🛠️

usage: openstack messaging queue create [-h] [-f {json,shell,table,value,yaml}]
                                        [-c COLUMN] [--max-width <integer>] [--noindent]
                                        [--prefix PREFIX]
                                        <queue_name>

Create a queue. ✨

Positional arguments:

  • <queue_name> — Name of the queue.

🗑️ openstack messaging queue delete 🗑️

usage: openstack messaging queue delete [-h] <queue_name>

Delete a queue.

Positional arguments:

  • <queue_name> — Name of the queue.

🔍 openstack messaging queue get metadata 🔍

usage: openstack messaging queue get metadata [-h] [-f {json,shell,table,value,yaml}]
                                              [-c COLUMN] [--max-width <integer>]
                                              [--noindent] [--prefix PREFIX]
                                              <queue_name>

Get queue metadata.

Positional arguments:

  • <queue_name> — Name of the queue.

📋 openstack messaging queue list 📋

usage: openstack messaging queue list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN]
                                      [--max-width <integer>] [--noindent]
                                      [--quote {all,minimal,none,nonnumeric}]
                                      [--marker <queue_id>] [--limit <limit>]
                                      [--detailed]

List available queues.

Optional arguments:

  • --marker <queue_id> — Queue's paging marker.
  • --limit <limit> — Page size limit.
  • --detailed — If show detailed information of queue.

✍️ openstack messaging queue set metadata ✍️

usage: openstack messaging queue set metadata [-h] <queue_name> <queue_metadata>

Set queue metadata. All the metadata of the queue will be replaced by queue_metadata. like, full glow-up replacement, no leftovers. 💅

Positional arguments:

  • <queue_name> — Name of the queue.
  • <queue_metadata> — Queue metadata. It should be json like. For example: '{"age": 18}'

🔗 openstack messaging queue signed url 🔗

usage: openstack messaging queue signed url [-h] [-f {json,shell,table,value,yaml}]
                                            [-c COLUMN] [--max-width <integer>]
                                            [--noindent] [--prefix PREFIX]
                                            [--paths <paths>]
                                            [--ttl-seconds <ttl_seconds>]
                                            [--methods <methods>]
                                            <queue_name>

Create a pre-signed url for the queue.

Positional arguments:

  • <queue_name> — Name of the queue.

Optional arguments:

  • --paths <paths> — Allowed paths in a comma-separated list. Options: messages, subscriptions, claims.
  • --ttl-seconds <ttl_seconds> — Length of time (in seconds) until the signature expires.
  • --methods <methods> — HTTP methods to allow as a comma-separated list. Options: GET, HEAD, OPTIONS, POST, PUT, DELETE.

openstack messaging queue stats

usage: openstack messaging queue stats [-h] [-f {json,shell,table,value,yaml}]
                                      [-c COLUMN] [--max-width <integer>] [--noindent]
                                      [--prefix PREFIX]
                                      <queue_name>

Okay so this one gets you the queue stats, bestie. That's the whole vibe.

Positional arguments:

  • <queue_name> — name of the queue 💅

openstack messaging queue purge

usage: openstack messaging queue purge [-h] [--resource_types <resource_types>]
                                      <queue_name>

Purge a queue. Important: all the metadata of the queue will be kept — so it's not a full delete situation, it's a "clear the stuff inside" situation. Use --resource_types to specify which resource should be purged (the page says "pured", love that for it). If --resource_types is not specified, all the messages and subscriptions in the queue will be purged by default. That's the default, no cap.

Positional arguments:

  • <queue_name> — name of the queue 🌸

Optional arguments:

  • --resource_types <resource_types> — resource types you want to be purged. It supports messages and subscriptions. 🫶

🩺 Health

For help on a specific openstack messaging message command, enter:

$ openstack messaging message COMMAND -h/--help

The one command:

messaging message list
messaging message post

(Yes, it says "the one command" and then lists two. We're not gonna fight the manpage about it. 😭)

openstack messaging message list

usage: openstack messaging message list [-h] [-f {csv,json,table,value,yaml}]
                                      [-c COLUMN]
                                      [--quote {all,minimal,none,nonnumeric}]
                                      [--noindent] [--max-width <integer>]
                                      [--fit-width] [--print-empty]
                                      [--sort-column SORT_COLUMN]
                                      [--message-ids <message_ids>]
                                      [--limit <limit>] [--echo]
                                      [--include-claimed]
                                      [--include-delayed]
                                      [--client-id <client_id>]
                                      <queue_name>

List all of the messages in a queue. That's it, that's the job. The usage line above is where all the flag energy lives — formatting, sorting, filtering, all of it. ✨

Positional arguments:

  • <queue_name> — name of the queue 🎀

openstack messaging message post

usage: openstack messaging message post [-h] [--client-id <client_id>]
                                      <queue_name> <messages>

Post the messages to a queue. Very demure, very mindful.

Positional arguments:

  • <queue_name> — name of the queue 🦋
  • <messages> — messages. It should be json like. For example: '[{"body": "msg", "ttl": 60}]' — yes, keep the JSON exactly like that. 🔥

🎯 Claim

For help on a specific openstack messaging claim command, enter:

$ openstack messaging claim COMMAND -h/--help

The eight commands:

messaging claim create
messaging claim query
messaging claim release
messaging claim renew

(The page says eight, the list shows four. Iconic inconsistency. We move. 💀)

openstack messaging claim create

usage: openstack messaging claim create [-h] [-f {csv,json,table,value,yaml}]
                                      [-c COLUMN] [--max-width <integer>] [--noindent]
                                      [--quote {all,minimal,none,nonnumeric}]
                                      [--ttl <ttl>] [--grace <grace>]
                                      [--limit <limit>]
                                      <queue_name>

Create claim and return a list of claimed messages. Claiming messages, but make it cute. 👑

Positional arguments:

  • <queue_name> — name of the queue to be claim. (The page says "to be claim" — we're keeping the lore.) 💖

Optional arguments:

  • --ttl <ttl> — time to live in seconds for claim ⭐
  • --grace <grace> — the message grace period in seconds 🌈
  • --limit <limit> — claims a set of messages, up to limit 🍓

openstack messaging claim query

usage: openstack messaging claim query [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN]
                                      [--max-width <integer>] [--noindent]
                                      [--quote {all,minimal,none,nonnumeric}]
                                      <queue_name> <claim_id>

Display claim details. Detective mode: activated. 🔍

Positional arguments:

  • <queue_name> — name of the claimed queue 💜
  • <claim_id> — ID of the claim 🎀

openstack messaging claim release

usage: openstack messaging claim release [-h] <queue_name> <claim_id>

Delete a claim. Let it go, bestie. 🦋

Positional arguments:

  • <queue_name> — name of the claimed queue 🌸
  • <claim_id> — claim ID to delete 💅

openstack messaging claim renew

usage: openstack messaging claim renew [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN]
                                      [--max-width <integer>] [--noindent]
                                      [--quote {all,minimal,none,nonnumeric}]
                                      [--ttl <ttl>] [--grace <grace>]
                                      <queue_name> <claim_id>

Renew a claim. Giving that claim a little extension, main character energy. ✨

Positional arguments:

  • <queue_name> — name of the claimed queue 🫶
  • <claim_id> — claim ID 👑

Optional arguments:

  • --ttl <ttl> — time to live in seconds for claim ⭐
  • --grace <grace> — the message grace period in seconds 🌈

🏊 Pool

For help on a specific openstack messaging pool command, enter:

$ openstack messaging pool COMMAND -h/--help

The ten commands:

messaging pool create
messaging pool delete
messaging pool list
messaging pool show
messaging pool update

(Again: says ten, lists five. The math is not mathing, but we're still slaying. 💀)

openstack messaging pool create

usage: openstack messaging pool create [-h] [-f {json,shell,table,value,yaml}]
                                      [-c COLUMN] [--max-width <integer>] [--noindent]
                                      [--prefix PREFIX] [--pool_group <pool_group>]
                                      [--pool_options <pool_options>]
                                      <pool_name> <pool_uri> <pool_weight>

Create a pool. Pool girl summer. 🩷

Positional arguments:

  • <pool_name> — name of the pool 🎀
  • <pool_uri> — storage engine URI 🌸
  • <pool_weight> — weight of the pool ⭐

Optional arguments:

  • --pool_group <pool_group> — group of the pool 💖
  • --pool_options <pool_options> — an optional request component related to storage-specific options 🦋

openstack messaging pool delete

usage: openstack messaging pool delete [-h] <pool_name>

Delete a pool. Bye bestie. 👋

Positional arguments:

  • <pool_name> — name of the pool 💅

openstack messaging pool list

usage: openstack messaging pool list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN]
                                      [--max-width <integer>] [--noindent]
                                      [--quote {all,minimal,none,nonnumeric}]
                                      [--marker <pool_name>] [--limit <limit>]
                                      [--detailed <detailed>]

List available Pools. Capital P, because it's that serious. 🔥

Optional arguments:

  • --marker <pool_name> — pool's paging marker 🫶
  • --limit <limit> — page size limit 🍓
  • --detailed <detailed> — detailed output ✨

openstack messaging pool show

usage: openstack messaging pool show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN]
                                      [--max-width <integer>] [--noindent]
                                      [--prefix PREFIX]
                                      <pool_name>

Display pool details. Show me everything. 👀

Positional arguments:

  • <pool_name> — pool to display (name) 💜

openstack messaging pool update

usage: openstack messaging pool update [-h] [-f {json,shell,table,value,yaml}]
                                      [-c COLUMN] [--max-width <integer>] [--noindent]
                                      [--prefix PREFIX] [--pool_uri <pool_uri>]
                                      [--pool_weight <pool_weight>]
                                      [--pool_group <pool_group>]
                                      [--pool_options <pool_options>]
                                      <pool_name>

Update a pool attribute. Glow-up era. 🌟

Positional arguments:

  • <pool_name> — name of the pool 🎀

Optional arguments:

  • --pool_uri <pool_uri> — storage engine URI 🌸
  • --pool_weight <pool_weight> — weight of the pool ⭐
  • --pool_group <pool_group> — group of the pool 💖
  • --pool_options <pool_options> — an optional request component related to storage-specific options 🦋

🍓 Flavor

For help on a specific openstack messaging flavor command, enter:

$ openstack messaging flavor COMMAND -h/--help

The five commands:

messaging flavor create
messaging flavor delete
messaging flavor list
messaging flavor show
messaging flavor update

openstack messaging flavor create

usage: openstack messaging flavor create [-h]
                                      [-f {json,shell,table,value,yaml}]
                                      [-c COLUMN] [--max-width <integer>]
                                      [--noindent] [--prefix PREFIX]
                                      [--capabilities <capabilities>]
                                      <flavor_name> <pool_group>

Create a pool flavor. Yes, flavor. Not the edible kind, unfortunately. 🍓

Positional arguments:

  • <flavor_name> — name of the flavor 🎀
  • <pool_group> — pool group for flavor 💜

Optional arguments:

  • --capabilities <capabilities> — describes flavor-specific capabilities. This option is only available in client api version < 2. 🫶

openstack messaging flavor delete

usage: openstack messaging flavor delete [-h] <flavor_name>

Delete a pool flavor. No more flavor. 💀

Positional arguments:

  • <flavor_name> — name of the flavor 🌸

openstack messaging flavor list

usage: openstack messaging flavor list [-h] [-f {csv,json,table,value,yaml}]
                                      [-c COLUMN] [--max-width <integer>]
                                      [--noindent]
                                      [--quote {all,minimal,none,nonnumeric}]
                                      [--marker <flavor_name>]
                                      [--limit <limit>]
                                      [--detailed <detailed>]

List available pool flavors. A little flavor lineup. ✨

Optional arguments:

  • --marker <flavor_name> — flavor's paging marker 🦋
  • --limit <limit> — page size limit 🍓
  • --detailed <detailed> — if show detailed capabilities of flavor 💅

openstack messaging flavor show

usage: openstack messaging flavor show [-h] [-f {json,shell,table,value,yaml}]
                                       [-c COLUMN] [--max-width <integer>]
                                       [--noindent] [--prefix PREFIX]
                                       <flavor_name>

Okay so this one just displays flavor details — like, the whole vibe of one flavor, front to back. 💅

Positional arguments:

  • <flavor_name> — the flavor you wanna display, by name.

Optional arguments:

  • -h — help, bestie. always there for u 🫶
  • -f {json,shell,table,value,yaml} — pick your output format ✨
  • -c COLUMN — only show these column(s)
  • --max-width <integer> — cap the width of the output
  • --noindent — no indenting for json/yaml 🎀
  • --prefix PREFIX — prefix to slap on all the output names

openstack messaging flavor update

usage: openstack messaging flavor update [-h]
                                         [-f {json,shell,table,value,yaml}]
                                         [-c COLUMN] [--max-width <integer>]
                                         [--noindent] [--prefix PREFIX]
                                         [--pool_group <pool_group>]
                                         [--capabilities <capabilities>]
                                         <flavor_name>

Update a pool flavor's attributes. ✨ little glow-up for your flavor, no biggie.

Positional arguments:

  • <flavor_name> — name of the flavor, obvs.

Optional arguments:

  • -h — help 💖
  • -f {json,shell,table,value,yaml} — output format, ur choice bestie
  • -c COLUMN — columns to show
  • --max-width <integer> — max width of the output
  • --noindent — don't indent json/yaml
  • --prefix PREFIX — prefix for all output names
  • --pool_group <pool_group> — the pool group the flavor sits on 🪑
  • --capabilities <capabilities> — describes flavor-specific capabilities 🔥

💫 PING 💫

Wanna help on a specific openstack messaging ping command? Just type:

$ openstack messaging ping COMMAND -h/--help

And there is exactly one command here, main character energy only:

messaging ping

openstack messaging ping

usage: openstack messaging ping [-h] [-f {json,shell,table,value,yaml}]
                                [-c COLUMN] [--max-width <integer>]
                                [--noindent] [--prefix PREFIX]

Check if the Zaqar server is alive or not. 🫶 like a little "u up?" text for your server. if it answers, it's alive, slay.

  • -h — help
  • -f {json,shell,table,value,yaml} — output format
  • -c COLUMN — columns
  • --max-width <integer> — max width
  • --noindent — no indent for json/yaml
  • --prefix PREFIX — output name prefix
Heads up: this one has no positional arguments — you literally just run it and it vibes. 🌈

🩺 HEALTH 🩺

Help for a specific openstack messaging health command:

$ openstack messaging health COMMAND -h/--help

Again, just the one:

messaging health

openstack messaging health

usage: openstack messaging health [-h]

Display detailed health status of Zaqar server. 🎀 the full checkup, not just "are u alive" — the detailed tea.

  • -h — help
Not me pointing out this one doesn't even take -f or -c 😭 it's literally just -h. minimal queen.

🌸 SUBSCRIPTION 🌸

Help for a specific openstack messaging subscription command:

$ openstack messaging subscription COMMAND -h/--help

The ten commands:

messaging subscription create
messaging subscription delete
messaging subscription list
messaging subscription show
messaging subscription update
She says ten and then lists five and honestly? We're not gonna fact-check her 💀 the page says ten, the list says five, that's the lore. 🙈

openstack messaging subscription create

usage: openstack messaging subscription create [-h]
                                                [-f {json,shell,table,value,yaml}]
                                                [-c COLUMN] [--max-width <integer>]
                                                [--noindent] [--prefix PREFIX]
                                                [--options <options>]
                                                <queue_name> <subscriber> <ttl>

Create a subscription. 💖 new sub, who dis.

Positional arguments:

  • <queue_name> — name of the queue
  • <subscriber> — the subscriber that will be notified 🔔
  • <ttl> — time to live of the subscription, in seconds ⏳

Optional arguments:

  • -h — help
  • -f {json,shell,table,value,yaml} — output format
  • -c COLUMN — columns
  • --max-width <integer> — max width
  • --noindent — no indent for json/yaml
  • --prefix PREFIX — output name prefix
  • --options <options> — options for the subscription

openstack messaging subscription delete

usage: openstack messaging subscription delete [-h] <queue_name> <subscription_id>

Delete a subscription. 💀 bye bestie, unfollowed.

Positional arguments:

  • <queue_name> — name of the queue
  • <subscription_id> — ID of the subscription
Notice: no format flags here. It just takes -h and goes. efficient icon ✨

openstack messaging subscription list

usage: openstack messaging subscription list [-h] [-f {csv,json,table,value,yaml}]
                                             [-c COLUMN] [--max-width <integer>]
                                             [--noindent]
                                             [--quote {all,minimal,none,nonnumeric}]
                                             [--marker <subscription_id>]
                                             [--limit <limit>]
                                             <queue_name>

Get list of subscriptions. 🦋 the whole roster.

Positional arguments:

  • <queue_name> — name of the queue

Optional arguments:

  • -h — help 🫶
  • -f {csv,json,table,value,yaml} — output format (yes, csv is in this one's list 👀)
  • -c COLUMN — columns
  • --max-width <integer> — max width
  • --noindent — no indent for json/yaml
  • --quote {all,minimal,none,nonnumeric} — when to quote stuff in csv 🎀
  • --marker <subscription_id> — the marker, a subscription ID
  • --limit <limit> — how many to return, max

openstack messaging subscription show

usage: openstack messaging subscription show [-h] [-f {json,shell,table,value,yaml}]
                                             [-c COLUMN] [--max-width <integer>]
                                             [--noindent] [--prefix PREFIX]
                                             <queue_name> <subscription_id>

Query a subscription details. 🔍 the full scoop on one sub.

Positional arguments:

  • <queue_name> — name of the queue
  • <subscription_id> — ID of the subscription

Optional arguments:

  • -h — help
  • -f {json,shell,table,value,yaml} — output format
  • -c COLUMN — columns
  • --max-width <integer> — max width
  • --noindent — no indent for json/yaml
  • --prefix PREFIX — output name prefix

openstack messaging subscription update

usage: openstack messaging subscription update [-h]
                                               [-f {json,shell,table,value,yaml}]
                                               [-c COLUMN] [--max-width <integer>]
                                               [--noindent] [--prefix PREFIX]
                                               [--subscriber <subscriber>] [--ttl <ttl>]
                                               [--options <options>]
                                               <queue_name> <subscription_id>

Update a subscription. 💅 glow-up szn.

Positional arguments:

  • <queue_name> — name of the queue
  • <subscription_id> — ID of the subscription

Optional arguments:

  • -h — help
  • -f {json,shell,table,value,yaml} — output format
  • -c COLUMN — columns
  • --max-width <integer> — max width
  • --noindent — no indent for json/yaml
  • --prefix PREFIX — output name prefix
  • --subscriber <subscriber> — subscriber that will be notified 🔔
  • --ttl <ttl> — time to live of the subscription, in seconds ⏳
  • --options <options> — metadata of the subscription, in JSON format 🎀

📝 RELEASE NOTES 📝

New Release Note

We use reno to publish the release note now. Please see Release Page https://docs.openstack.org/releasenotes/python-zaqarclient for more detail. 🦋

0.2.0

  • 1934a98 Updated from global requirements
  • 863371b Allow for authentication in functional tests
  • b35689d Don't pass options to pool creation
  • 8104ff4 Don't reuse request and transport instances
  • bf841b5 Pass group in pool's functional tests
  • 2490ed4 Send claims limit as a query param
  • baf6fa7 v1.1 and v2 claims return document not list
  • 0d80728 Make sure the API version is passed down
  • 407925c Make v1.1 the default CLI version
  • 895aad2 Updated from global requirements
  • 8a81c44 Updated from global requirements
  • 705ee75 Implement CLI support for flavor
  • 32a847e Implements CLI for pool
  • 964443d Raises an error if the queue name is empty
  • e9a8d01 Added support to pools and flavors
  • f46979b Removed deprecated 'shard' methods
  • 1a85f83 Update README to work with release tools

0.1.1

  • Fix handling of 1.1 API
  • Gets 'flavor' data if the resource exists
  • Gets 'pool' data if the resource exists
  • Handling exception on 504 Error
  • Added i18n support
  • Makes health return True or False
  • Add reference docs for latest recommended client
  • Add docs for Client instances
  • Add a read-only property for Queues

🔎 Indices and tables

  • Index <>
  • Module Index <>
  • Search Page <>

💜 Author

Author name not set 🙈 (yes, really — that's literally what it says, no cap)

2010-present, OpenStack Foundation — iconic, timeless, mother. 👑

And that's the whole page bestie!! 🎀✨ It's from python-zaqarclient, version 4.7.0, dated Jan 02, 1980 — yes, 1980, she's vintage 💀🦋 — and it's all officially brought to you by the OpenStack Foundation. slay, go message some queues, ily, bye!! 💖🌈🫶

📦 where this page comes from