Flipt Cloud to Flipt v2

​

Prerequisites

• An active Flipt Cloud account with configured environments
• A GitHub repository containing your feature flag data (managed by Flipt Cloud)
• Flipt v2 installed on your target environment
• Access to the GitHub repository containing your feature flag data

​

Migration Overview

​

1. Identify Your Flipt Cloud Repository

1. Log into your Flipt Cloud dashboard
2. Navigate to your environment settings
3. Click on the Integrations tab
4. Click on the ‘View GitHub Repository’ button
5. Note the following information:
   • Repository URL: The GitHub repository where your flags are stored
   • Branch: The branch being used (typically main)
   • Directory: The directory path within the repository (if any)

​

2. Export Authorization Configuration

1. While logged into Flipt Cloud, click on the Settings tab
2. Click on the Roles tab
3. Click on the Export RBAC button
4. Download the authorization configuration archive and save it for later

​

3. Set Up GitHub Authentication

1. Go to GitHub Settings > Developer settings > Personal access tokens
2. Click “Generate new token”
3. Give your token a descriptive name (e.g., “Flipt v2 Migration”)
4. Select the appropriate resource owner and repositories
5. Set an expiration date
6. Select the following repository scopes:
   • repo read and write access (for private repositories)
   • contents read and write access
7. Click “Generate token” and copy the token

​

4. Configure Flipt v2

​

Add GitHub Credentials

credentials:
  github:
    type: access_token
    access_token: ${env:GITHUB_TOKEN}

​

Configure Storage Backend

storage:
  github:
    remote: "https://github.com/<your-username>/<your-repo>.git"
    branch: "main"
    poll_interval: "30s"
    credentials: "github"
    backend:
      type: local
      path: "/tmp/flipt-repo"

• <your-username> and <your-repo> with your actual GitHub repository details
• branch with the branch used by Flipt Cloud (if different from main)
• path with your preferred local storage location

​

Configure Environments

environments:
  production:
    name: "Production"
    storage: "github"
    default: true
    directory: "production" # Use the same directory as Flipt Cloud
  staging:
    name: "Staging"
    storage: "github"
    directory: "staging" # Use the same directory as Flipt Cloud

​

Configure Authorization

package flipt.authz.v2

import rego.v1

default allow := false

allow if {
	some rule in has_rules

	permit_string(rule.resource, input.request.resource)
	permit_slice(rule.actions, input.request.action)
	permit_string(rule.namespace, input.request.namespace)
}

authorization:
  required: true
  local:
    policy:
      path: "policy.rego"
    data:
      path: "data.json"

​

5. Start Flipt v2

1. Set your GitHub token as an environment variable:
   Copy

   Ask AI

   export GITHUB_TOKEN=your_github_token_here
   

2. Start Flipt v2 with your configuration:
   Copy

   Ask AI

   ./flipt server --config config.yaml
   

3. Flipt v2 will:
   • Clone your existing repository
   • Load your feature flag data
   • Begin syncing with GitHub

​

6. Verify Migration

1. Access the Flipt v2 UI (typically at http://localhost:8080)
2. Verify that all your feature flags, segments, and rules are present
3. Check that all environments are configured correctly
4. Test flag evaluation to ensure everything works as expected

​

7. Update Your Applications

1. Update SDK Configuration: Change the Flipt server URL in your application code
2. Update API Keys: Generate new Static Tokens in Flipt v2 if needed
3. Test Evaluation: Verify that flag evaluation works with your new instance

​

8. Decommission Flipt Cloud

1. Update any remaining applications to use Flipt v2
2. When ready, you can delete your Flipt Cloud environment

​

Data Continuity

• Flipt Cloud stores data in your GitHub repository
• Flipt v2 reads from the same repository structure
• No data transformation or conversion is required
• All flag history is preserved in Git

​

Troubleshooting

​

Repository Access Issues

• Verify your GitHub token has the correct permissions
• Check that the repository URL is correct
• Ensure the branch name matches what Flipt Cloud was using
• Ensure the directory path matches what Flipt Cloud was using

​

Sync Issues

• Check the poll_interval setting
• Verify write permissions on the local storage path
• Verify your GitHub token as the correct scopes (write access to the repository)
• Review Flipt v2 logs for sync errors

​

Next Steps

• Configure authentication for your team
• Set up environments for your deployment pipeline
• Review configuration settings for your deployment
• Setup Merge Proposals for your environments

​

Support

• Check the Flipt v2 documentation
• Join our Discord community
• Visit GitHub Discussions

• Flipt v2 Storage Configuration
• Git Sync with GitHub
• Flipt Cloud Git-Backed Storage