An application is deployed where it has subscriptions.
Overview
The "Deployments" page section further enables the management and deployment of API-driven applications.
Deployments of the API
management platform is designed to manage the deployment of an application, in this case, "Car Finder," to various environments. The page displays deployment information and provides controls for managing these deployments.Interface Sections
General: This vertical navigation pane on the left allows users to switch between different application management options, such as overview, subscriptions, analytics, deployments, custom fields, and settings.
Deployment Information
Environment Category: At the top of the main pane, the "PRODUCTION" label indicates that the deployments listed below are intended for production environments.
Deployment Instance: Below the environment category, we have:
API Gateway Instance: Shows the name of the API gateway ("Gravitee") where the application is deployed.
Agent Status: Indicates whether there is a monitoring agent associated with this deployment, which in this case is "No Agent."
Gateway ID: Provides a unique identifier for the gateway instance, likely to be used for referencing in logs, configurations, or support tickets.
Interface Features
Deployment Action Button: The "Deploy" button in the top right suggests that users can initiate a new deployment process from this page.
The primary focus is on the production environment. This signals the stage of development the application is in and provides a gateway for managing live services.
Below this header, a customizable tag for each Deployment serves as a quick visual reference for users navigating through multiple deployments.
Adjacent to the tag, a box outlines a deployment descriptor, "No Agent," which suggests that the current deployment does not have an active agent assigned to it. An agent in this context could be a service or a module that performs actions on behalf of the deployment, such as monitoring or traffic management.
Further details are provided in the form of a unique identifier for the gateway: This identifier is essential for tracking and managing specific deployments, especially when dealing with numerous instances across different environments.
To the top right corner of the interface is a "Deploy" button, initiating the deployment process or update the current deployment state. In order to deploy an Application, it must be subscribed to.
Table of contents
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|