diff options
| author | Matthieu Huin <mhuin@redhat.com> | 2022-04-14 11:40:36 +0200 |
|---|---|---|
| committer | Matthieu Huin <mhuin@redhat.com> | 2022-05-19 15:35:30 +0200 |
| commit | 57c78c08e1b9ee12d36f13cf45384f21354435b5 (patch) | |
| tree | 9f9cbedff7a3a9ca2764a9e4390724c54b7bf794 /setup.cfg | |
| parent | f2297cadb07fedbde168afe791c7be6a0ca6ebb4 (diff) | |
| download | zuul-57c78c08e1b9ee12d36f13cf45384f21354435b5.tar.gz | |
Clarify zuul admin CLI scope
We have two CLIs: zuul-client for REST-related operations, which cover
tenant-scoped, workflow modifying actions such as enqueue, dequeue and
promote; and zuul which supercedes zuul-client and covers also true admin
operations like ZooKeeper maintenance, config checking and issueing auth tokens.
This is a bit confusing for users and operators, and can induce code
duplication.
* Rename zuul CLI into zuul-admin. zuul is still a valid endpoint
and will be removed after next release.
* Print a deprecation warning when invoking the admin CLI as zuul
instead of zuul-admin, and when running autohold-*, enqueue-*,
dequeue and promote subcommands. These subcommands will need to be
run with zuul-client after next release.
* Clarify the scopes and deprecations in the documentation.
Change-Id: I90cf6f2be4e4c8180ad0f5e2696b7eaa7380b411
Diffstat (limited to 'setup.cfg')
| -rw-r--r-- | setup.cfg | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -29,6 +29,7 @@ console_scripts = zuul-scheduler = zuul.cmd.scheduler:main zuul-merger = zuul.cmd.merger:main zuul = zuul.cmd.client:main + zuul-admin = zuul.cmd.client:main zuul-executor = zuul.cmd.executor:main zuul-bwrap = zuul.driver.bubblewrap:main zuul-web = zuul.cmd.web:main |