🚨 Shai-Hulud Strikes Again:834 Packages Compromised.Technical Analysis →
Socket
Book a DemoInstallSign in
Socket

@axway/amplify-central-apigee-extension

Package Overview
Dependencies
Maintainers
14
Versions
10
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@axway/amplify-central-apigee-extension

Create AMPLIFY Central resources from Apigee API Proxies

npmnpm
Version
0.0.3-dev.2
Version published
Weekly downloads
0
-100%
Maintainers
14
Weekly downloads
 
Created
Source

@axway/amplify-central-apigee-extension

AMPLIFY Central CLI extension for downloading and creating AMPLIFY Central resources for Apigee.

For more documentation and examples please visit Unified Catalog integrations.

Disclaimer

This extension is example code and comes with no guarantee of support or maintenance.

PreReqs

This assumes you already have npm installed and have an apigee account setup. Visit NodeJS to learn how to install NodeJS. If you need help with setting up your apigee account, you can view the Setup section of the local DEVREADME.MD

Installation

Assuming you are familiar with Node.js and npm, you should first install the Axway AMPLIFY CLI, which will give you connectivity to the Axway AMPLIFY Platform. Note that you must first have an account on https://platform.axway.com, and be provisioned in AMPLIFY Central:

$ [sudo] npm install -g @axway/amplify-cli

Use the AMPLIFY package manager command to install the AMPLIFY Central CLI:

$ amplify pm install @axway/amplify-central-cli

You can then install the @axway/amplify-central-apigee-extension:

$ npm install @axway/amplify-central-apigee-extension
$ amplify central config set extensions.apigee <path to where you installed module>

Getting started

You must be logged into the Axway AMPLIFY Platform before uploading any generated resource files. You'll also need to setup a Service (DOSA) account. To find out how to create one visit Get started with AMPLIFY CLI. Log in to the Axway AMPLIFY Platform using the following command:

$ amplify auth login --client-id <DOSA Service Account> --secret-file <Private Key>

To see available help, options and examples add -h or --help option on any command:

$ amplify auth logout -h

General usage

There are two main extension commands; config and resources. You can run each command with a -h to get help on that specific command.

$ amplify central apigee-extension -h
USAGE: amplify central apigee-extension <command> [options]

Create AMPLIFY Central resources from Apigee API Management APIs

AMPLIFY CENTRAL EXTENSION FOR APIGEE API MANAGEMENT COMMANDS:
  config  Manage Apigee Extension Configuration
  resources  Generate resources from Apigee API Management APIs

Commands reference:

CONFIG

The config command is utilized to configure the extension prior to generating resources. There are two config sub-commands; list and set.

$ amplify central apigee-extension config -h
USAGE: amplify central apigee-extension config <command> [options]

Manage Apigee Extension Configuration

CONFIG COMMANDS:
  list  View AMPLIFY Central apigee-extension configuration
  set  Set AMPLIFY Central apigee-extension configuration

 SET OPTIONS:
  --environment-name=<value>  Required: Set environment name to create
  --icon=<value>  Set absolute path for custom icon
  --organization-id=<value>  Required: Set your Apigee Organization ID
  --output-dir=<value>  Set absolute path for output directory
  --password=<value>  Required: Set your Apigee Password
  --username=<value>  Required: Set your Apigee Username

config examples:

# set output dir for the generated resources:
$ amplify central apigee-extension config set --output-dir=<directory>
# view config:
$ amplify central apigee-extension config list
# view list of available options
$ amplify central apigee-extension config set -h

SET OPTIONS:
  --environment-name=<value>  Set environment name to create
  --icon=<value>  Set absolute path for custom icon
  --organization-id=<value>  Set your Apigee Organization ID
  --output-dir=<value>  Set absolute path for output directory
  --password=<value>  Set your Apigee Password
  --username=<value>  Set your Apigee Username

RESOURCES

The resources command is utilized to generate apigee resources for Central. There is one resources sub-command: generate

$ amplify central apigee-extension resources -h

USAGE: amplify central apigee-extension resources <command> [options]

Generate resources from Apigee API Management APIs

RESOURCES COMMANDS:
  generate

resources examples:

$ amplify central apigee-extension resources generate

Generated Files

The generate command will create AMPLIFY Central resource files for your configured Apigee instance. These files will generated into either ./resources or the directory you configured with the --output-dir configuration setting.

After generating these files you can modify and upload them to AMPLIFY Central with the amplify central create -f=<file> command. You'll want be sure to upload any Environment files before other generate resources.

$ amplify central create -h
USAGE: amplify central create <command> [options]

Create a resource from a file. JSON and YAML formats are accepted.

CREATE COMMANDS:
  environment   Create an environment with the specified name.

CREATE OPTIONS:
  --client-id=<value>   Override your DevOps account's client ID
  -f,--file=<path>      Filename to use to create the resource
  -o,--output=<value>   Additional output formats. One of: yaml | json

create example:

# Upload the Environment, Webhook, and ConsumerSubscriptionDefinition
amplify central create -f=~/Desktop/Environment.yaml
# Upload the APIService, APIServiceRevision, APIServiceInstance, and ConsumerInstance
amplify central create -f=~/Desktop/APIService-swagger-petstore.yaml

Author

Axway support@axway.com https://axway.com

License

Copyright 2020 Axway

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Keywords

axway

FAQs

Package last updated on 22 Oct 2020

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts