Add Environment to Config file
Add new environment and its related endpoints to the config file
apictl add env [environment] [flags]
apictl add env production \
--apim https://localhost:9443
apictl add env dev \
--mi https://localhost:9164
apictl add env prod \
--apim https://apim.com:9443 \
--mi https://localhost:9164
apictl add env test \
--registration https://idp.com:9443 \
--publisher https://apim.com:9443 \
--devportal https://apps.com:9443 \
--admin https://apim.com:9443 \
--token https://gw.com:9443/oauth2/token \
--mi https://localhost:9164
apictl add env dev \
--apim https://apim.com:9443 \
--registration https://idp.com:9443 \
--token https://gw.com:9443/oauth2/token
You can either provide only the flag --apim , or all the other 4 flags (--registration --publisher --devportal --admin) without providing --apim flag.
If you are omitting any of --registration --publisher --devportal --admin flags, you need to specify --apim flag with the API Manager endpoint. In both of the
cases --token flag is optional and use it to specify the gateway token endpoint. This will be used for "apictl get-keys" operation.
To add a micro integrator instance to an environment you can use the --mi flag.
--admin string Admin endpoint for the environment
--apim string API Manager endpoint for the environment
--devportal string DevPortal endpoint for the environment
-h, --help help for env
--mi string Micro Integrator Management endpoint for the environment
--publisher string Publisher endpoint for the environment
--registration string Registration endpoint for the environment
--token string Token endpoint for the environment
-k, --insecure Allow connections to SSL endpoints without certs
--verbose Enable verbose mode
- apictl add - Add Environment to Config file