Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/SoftwareAG/webmethods-io-api-scripts

Scripts for working with webMethods.io API
https://github.com/SoftwareAG/webmethods-io-api-scripts

api cloud webmethods webmethods-io

Last synced: about 2 months ago
JSON representation

Scripts for working with webMethods.io API

Host: GitHub
URL: https://github.com/SoftwareAG/webmethods-io-api-scripts
Owner: SoftwareAG
License: apache-2.0
Created: 2019-10-16T09:24:09.000Z (almost 5 years ago)
Default Branch: master
Last Pushed: 2019-11-05T10:11:13.000Z (almost 5 years ago)
Last Synced: 2024-04-12T16:16:08.497Z (5 months ago)
Topics: api, cloud, webmethods, webmethods-io
Language: PowerShell
Homepage:
Size: 15.6 KB
Stars: 0
Watchers: 5
Forks: 0
Open Issues: 0
Metadata Files:
- Readme: README.md
- License: LICENSE

Awesome Lists containing this project

awesome-softwareag - webmethods-io-api-scripts - A collection of scripts for working with webMethods.io API. (Integration & APIs / ![icon-webMethods io-Integration-64x64](https://user-images.githubusercontent.com/23717841/230610242-388570ae-f593-4d12-b4d8-c70579261a3e.png) webMethods.io Integration)

README

# webmethods-io-api-scripts
Scripts for working with webMethods.io API
- `Export-Api.ps1` : Export a specific API version into the file system, e.g. to place it under version control for CI/CD

## Installation
Copy files to a location of your choice, preferably one that is part of the search path.

## API Export

Export a specific API version into the file system, e.g. to place it under version control for CI/CD

### Usage

Go the directory into which you want to have the API assets be placed. From there invoke the script to get all artifacts related to the specified API get exported. After that export the direcotry's contents can be put under version control (e.g. Git). From there they can be deployed to another tenant as part of CI/CD.

There is currently no check in place to validate that the specified combination of API name and API version returns only a single artifact. It is up to the user to ensure that only a single API instance is effectively being exported.

```
Export-Api [ {-Tenant | -BaseUrl }
-Username -Password
[ -CreateConfigFile [-ConfigFileName ] ]
-ApiName -ApiVersion ]
[-ApiIdFileName]
[-Verbose]
```

Options
- `-Tenant` : The following base URL will be used: `https://.gateway.webmethodscloud.com/rest/apigateway`. This is mutually exclusive with the `-BaseUrl` option.
- `-BaseUrl` : Specify an arbitrary base URL. This is mutually exclusive with the `-Tenant` option.
- `-Username` : Username to login with
- `-Password` : Password for username. Use single-quotes, if it contains special characters (incl. space)
- `-CreateConfigFile` : Create configuration file in current directory
- `-ConfigFileName` : Use custom name for creation of configuration file (default = .sag-cloud-api in current directory)
- `-ApiName` : API name to search for
- Use quotes, if it contains spaces
- Supports wildcards
- `-ApiVersion`
- `-ApiIdFileName`: Use custom name for file where API ID is stored during export (default = sag-cloud-api-id in current directory)
- `-Verbose` : In verbose mode the following information will be written to STDOUT
- Search parameters: Tenant, username, API name, API version
- Body of search request in JSON format
- Search result in JSON format
- UUID of API
- URI to trigger export

In non-verbose mode the script writes the UUID of the API to STDOUT.

### Examples

```
Export-Api -Tenant foobar
-Username user1 -Password 'secret'
-CreateConfigFile
-ApiName TestAPI -ApiVersion "1.0"
```
Will store the provided values in a configuration file in the current directory and then perform the export of the specified API and version. The UUID of the exported API will be written to the console.

```
Export-Api -Verbose
```
Read configuration file from current directory and perform the export with verbose output.

______________________
These tools are provided as-is and without warranty or support. They do not constitute part of the Software AG product suite. Users are free to use, fork and modify them, subject to the license agreement. While Software AG welcomes contributions, we cannot guarantee to include every contribution in the master project.