Deploy anywhere projects
Deploy anywhere projects are projects that are designed to manage deploy anywhere assets and configurations you create within an environment. The deploy anywhere projects have more capabilities when compared to your regular projects. Regular projects are the projects that are created within the tenant without the Develop Anywhere, Deploy Anywhere capability enabled.
Deploy anywhere projects support both your regular and deploy anywhere integrations, along with their associated configurations, unlike regular projects. You can initialize regular projects into deploy anywhere projects to save the deploy anywhere assets from that moment
If your tenant has the Develop Anywhere and Deploy Anywhere capability, new projects are created as deploy anywhere projects by default. Also, a package with the same name as the project is automatically created. From this package, you can import packages from other repositories and use in your project.
Furthermore, you can link deploy anywhere projects to external repositories.
Publish wizard for deploy anywhere projects
The Publish wizard does not list package services or deploy anywhere flow services if they are used by any integrations. However, when a project is published, all associated deploy anywhere assets are automatically included, regardless of whether those services were directly used in the integration.
Deploy wizard for deploy anywhere projects
The Deploy wizard for deploy anywhere projects includes the following pages in addition to the regular projects.
The Configure Git Account page lists all Git accounts configured in the tenant. You can choose one of the existing Git accounts from the drop-down list that is next to the package. In redeployments, the previously configured Git account is selected by default.
Also, you can create a new Git account by clicking the Add option next to the drop-down menu and use it for the project.
The Integration Runtimes page lists all runtimes that are configured for the package services. By default, the runtimes that are configured in the source environment are considered in the target environment during the first deployment. Otherwise, the most recently configured runtime is considered.
- The deploy anywhere flow services are not displayed in both the Configure Git Account and Integration Runtimes pages.
- For REST APIs, all resources are listed against the API name during deployment. For example, if the REST API has one resource with three resources (methods), then all three resources are displayed for that method. The service names in REST APIs that use packages are displayed in the format <Package service name>_/<resource path>_<method name>, for example, if the resource is Get, then the resource is displayed as Package1_/Path1_GET.
Also, in the Integration Runtimes page you have options to synchronize or restart runtimes after a successful deployment.
- Packages added to a project are not deployed if the target tenant does not support deploy anywhere assets.
- Packages added to a project are not exported or cloned when you export or clone an integration by using package services.
- When importing or deploying a project by using Public APIs, the new project name that is specified in the payload is ignored, and the original project name from the source environment is retained. After a successful deployment, the runtime configurations must be manually set in the target environment.
- After you import or export a project that includes package services, configure the runtimes in the target environment once the import completes successfully.
- REST APIs that use package services are not deployed to tenants where the develop anywhere, deploy anywhere capability is not enabled.
- Cloning REST APIs that use deploy anywhere flow services are not supported.