For an up-to-date list of the supported groups and commands, see the documentation.
The CLI is flexible and already provides a lot of commands & utility functions. To get a list of commands for each group call for instance apim app
| API-Id | Path | Name | Version | V-Host | State | Security | Policies | Organization | To get an overview about the groups just call apim: These can be accessed and discovered via the CLI on the basis of groups and their commands. The CLI is flexible and is extended with new functions via modules. When checked in, the CI/CD-Pipeline picks it up and replicates it into the API Manager. With that, an API developer or the operations team is just providing the desired state configuration of the API, Application. Watch this video (28 min): to get an overview + demo. The CLI transfers this desired state manually or automatically via a pipeline into the API management platform to become the actual state.Īdditionally the CLI supports basic administrative commands for instance to list and filter entities and perform simple tasks.
#Axway secure transport documentation code
Everything is declared as code in a config file and stored in your version management system. This CLI is following the same approach for your APIs, Applications, etc. This is used for instance to manage complex Cloud-Infrastructure called Infrastructure as code. A tool, like this CLI, is then replicating that declared state to become the actual state in the target environment. The basic idea for the so-called "Everything as code" approach is that the desired state of something (API, Application, etc.) is declared in a configuration file which stored in your version management system. The CLI is based on Swagger-Promote, which has been refactored to support more use-cases than only API-Import and -Export. You can call the CLI manually or integrate it into a CI/CD pipeline. This CLI allows you to control the Axway API management solution without access through the Web UI.
0 kommentar(er)
