Skip to Content
Deploying ApplicationsCreate application

Create application

Create a new application

The Core Platform dashboard is the preferred way to create a new application. It guides you through the same configuration that corectl creates from the command line:

  • A new repository
  • A template application demonstrating full continuous delivery:
    • Versioning
    • Functional testing
    • Non-functional testing
    • Promotion between a set of standard environments
    • Deployment to production

After completing the wizard and triggering the resulting GitHub workflow, you’ll have an application ready to deploy to production on every commit.

Using the dashboard

Open the dashboard and go to Applications then Create.

First, enter the application details. Choose the team that owns the application and, if your organisation uses systems, choose the system it belongs to.

Create application details in the dashboard

Next, choose the template. Application templates include the repository structure, sample app code, and Path to Production workflow defaults for common application types.

Choose an application template in the dashboard create application wizard

Then configure the deployment environment. Select the cluster set, choose whether the workload needs managed service access, and set replicas, resource requests, resource limits, and autoscaling defaults.

Configure application deployment environments in the dashboard

Review the generated configuration, then deploy it. The dashboard creates the repository and configuration change needed for the application to start using the Core Platform delivery workflow.

Using corectl

Use corectl when you prefer a terminal workflow or need to automate application creation.

corectl apps create <new-app-name> [<new-app-dir>]

To have Core Platform create workload identity cloud access for the application delivery unit, pass --cloud-access:

corectl apps create <new-app-name> [<new-app-dir>] --cloud-access

This adds a cloudAccess block to the generated delivery-unit configuration for the standard P2P namespaces.

new-app-name must be lower case, as Docker only allows lowercase letters for image names.

It will:

  • prompt you a few additional questions, including template for the application.
  • create a new repository using the selected template
  • configure the created GitHub repository, so P2P workflows will run without an issue

Developer workflow

Now you have an application deployed to production. You can make changes by raising PRs.

Raise a PR

Raising a PR will automatically build the app, push the docker image, and deploy it to environments for functional, non-functional, and integration testing.

Merge the PR

Merges to main by default do the same as a PR, and additionally deploy to a stable dev namespace that can be used for showcasing or integration testing.