
Product
Announcing Socket Certified Patches: One-Click Fixes for Vulnerable Dependencies
A safer, faster way to eliminate vulnerabilities without updating dependencies
@axway/amplify-central-apigee-extension
Advanced tools
Create AMPLIFY Central resources from Apigee API Proxies
Amplify Central CLI extension for downloading and creating Amplify Central resources for Apigee.
For more documentation and examples please visit Unified Catalog integrations.
This extension is example code and comes with no guarantee of support or maintenance.
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
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
Use the Amplify package manager command to install the Amplify Central CLI:
$ axway pm install @axway/axway-central-cli
You can then install the @axway/amplify-central-apigee-extension:
$ npm install @axway/amplify-central-apigee-extension
$ axway central config set extensions.apigee <path to where you installed module>
You must be logged into the Axway Amplify Platform before uploading any generated resource files. Refer to the Axway Central CLI documentation for more information.
There are two main extension commands; config and resources. You can run each command with a -h to get help on that specific command.
$ axway central apigee-extension -h
USAGE: axway 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
The config command is utilized to configure the extension prior to generating resources. There are two config sub-commands; list and set.
$ axway central apigee-extension config -h
USAGE: axway 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
# set output dir for the generated resources:
$ axway central apigee-extension config set --output-dir=<directory>
# view config:
$ axway central apigee-extension config list
# view list of available options
$ axway 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
The resources command is utilized to generate apigee resources for Central. There is one resources sub-command: generate
$ axway central apigee-extension resources -h
USAGE: axway central apigee-extension resources <command> [options]
Generate resources from Apigee API Management APIs
RESOURCES COMMANDS:
generate
$ axway central apigee-extension resources generate
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 axway central create -f=<file> command. You'll want be sure to upload any Environment files before other generate resources.
$ axway central create -h
USAGE: axway 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
# Upload the Environment, Webhook, and ConsumerSubscriptionDefinition
axway central create -f=~/Desktop/Environment.yaml
# Upload the APIService, APIServiceRevision, APIServiceInstance, and ConsumerInstance
axway central create -f=~/Desktop/APIService-swagger-petstore.yaml
Axway support@axway.com https://axway.com
Copyright 2021 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.
FAQs
Create AMPLIFY Central resources from Apigee API Proxies
We found that @axway/amplify-central-apigee-extension demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 19 open source maintainers collaborating on the project.
Did you know?

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.

Product
A safer, faster way to eliminate vulnerabilities without updating dependencies

Product
Reachability analysis for Ruby is now in beta, helping teams identify which vulnerabilities are truly exploitable in their applications.

Research
/Security News
Malicious npm packages use Adspect cloaking and fake CAPTCHAs to fingerprint visitors and redirect victims to crypto-themed scam sites.