Environment

Environments describe where code is deployed.

Each time Flinkwerk deploys a version of code to an environment, a deployment is created.

Flinkwerk allows you to configure various environments as part of your project. In such environment configurations, you can define which Git branch should be deployed to which cluster accessible under which custom domain.

Here's a sample project configuration of environments:

environments:
  staging:
    cluster: review
    only: branches
    except: env/production
  production:
    cluster: production-autopilot
    routes:
      - domain: 'flinkwerk.com'
        branch: env/production

Define environment controls

Flinkwerk environment controls follow the conventions of GitLab pipeline job controls.

To configure a Flinkwerk environment, you can use these directives:

• only
• except

For example, if you wanted to deploy all Git branches to a dedicated cluster named development, except for a branch named production, then you would configure your project's environments configuration like this:

environments:
  development:
    cluster: development
    only:
      - branches
    except:
      - production