8.3. OrgAdmin support - Axway-API-Management-Plus/apim-cli GitHub Wiki

Starting with version 1.5.0 also Organization-Administrators can use the tool to register APIs in API-Manager. This is basically supported with three different modes:

1. Unpublished APIs only
As long as an Organization-Administrator doesn't register/modify a "Published" API he can use the tool in the same way as an administrator.
However, everything that needs Admin-Permissions (like Quota-Settings, Client-Apps, etc.) can be configured by the Org-Admin but is ignored, as long a no Admin-User is provided.

2. Request for approval
Starting with version 1.6.5 this option is used by default, when executed without an Admin-Account.
When an Organization-Administrator tries to replicate a desired API with state: “Published”, Swagger-Promote will replicate that API into an actual state: "Request for approval" (Pending).
Once the API is in pending state, this basically becomes the actual API for the Organization-Administrator and he can update his actual API as often as he wants.
To get that API in production an Administrator must finally approve the pending API using the API-Manager UI or REST-API. Optionally it is recommended to automate that process and check regularly for pending APIs.
Once, the pending API has been approved, the actual published API becomes some kind of “invisible” for the Organization-Administrator. In other words: From Swagger-Promote perspective, there is basically no actual API anymore and any new replication request will result in a new pending API. From that point on the process starts from the beginning.

Important note:
As Swagger-Promote cannot manage the Production-API (published) using this mode (without having an Admin-Account), it therefore can’t manage configured Quotas, Client-Organizations and Application-Subscriptions. The Administrator has to take care to take over these entities from a previously existing published API.
Axway is working to improve Org-Admin permissions and once that is supported, also Swagger-Promote will support it.

3. Admin-Account configured
Another option for Org-Admins is to use Environment-Specific configuration files which may contain an Admin-Account. With that, everything the Org-Admin-Account can do is performed internally by the Org-Admin account, for all the rest, the Admin-Account is used. That means, that APIs automatically belong to the Org-Admin Organization, Org-Admins become the owner and appear in Audit-Logs.
The idea of this mode is to configure the Admin-Account on the CI/CD-System only to have it picked up when an OrgAdmin has initiated a CI/CD-Workflow.