Managing landscapes

A landscape is a logical collection of one or more environments that serve a common business purpose, such as development, QA, or production. Landscapes enables you to categorize and manage deployment targets according to business needs. When defining a deployment path, landscapes serve as a useful mechanism for selecting the appropriate environments for your release.

When creating a deployment environment, you can assign it to an existing landscape or create a new one as required. Environments can be added to or removed from a landscape as needed.

If a landscape contains multiple environments, those environments are considered peers within the landscape. Therefore, all inputs to those environments (nodes) must originate from the same landscape.

An environment can have a landscape as the target node in a deployment path.

Example Scenario:

You might have a landscape called Customer Acceptance that includes both a QA and a UAT environment. When deploying changes from a development environment for testing, you select the "Customer Acceptance" landscape as the target node in the deployment path, ensuring that both QA and UAT receive the same updates.