Project management

Focus: Master project management in Metric Store, including creating projects, managing repositories, working with branches, and configuring project settings. Project management in Metric Store enables you to organize your Cube definitions into separate projects, each with its own Git repository, branches, and deployment configuration. This allows you to manage different environments, features, and teams independently.

​

Creating projects

​

Project creation workflow

1. Navigate to Metric Store
   • Go to /metrics-store page
   • Or click “Metric Store” from navigation
2. Access project creation
   • If no projects exist: Click “Create project” button
   • If projects exist: Click project name in header → “New project”
3. Fill project details
   • Project name (required, unique, max 50 characters)
   • Repository type (Platform Managed or Imported)
   • Environment selection
   • Deployment options
   • Protected branches (optional)
4. Add project
   • Click “Add Project” button
   • Wait for repository cloning (if imported)
   • Project will be created and initialized

​

Repository types

​

Project settings

Project name

• Unique identifier for your project
• Maximum 50 characters
• Used for display and repository naming
• Can be edited after creation

Environment

• Select the environment where your data warehouse is configured
• Different environments can have different data sources
• Environment selection affects deployment and API access

Deployment options

• Always on - Service runs continuously
• On demand - Service starts when needed
• Scheduled - Time-based scheduling

See Deployment Options for detailed configuration. Protected branches

• Specify branches that should be protected from direct changes
• Protected branches typically require pull requests for changes
• Common choices: main, master, production

​

Editing projects

​

Edit project details

1. Access project settings
   • Click “Settings” button in header (gear icon)
   • Or click project name → “Edit project”
2. Modify settings
   • Edit project name
   • Change environment
   • Update deployment options
   • Modify protected branches
3. Save changes
   • Click “Save” to apply changes
   • Changes take effect immediately

​

Editable fields

• Project name - Update display name
• Environment - Change deployment environment
• Deployment options - Modify how service runs
• Protected branches - Add or remove protected branches

​

Read-only fields

• GitHub URL (for imported repos) - Cannot be changed after creation
• Subdirectory (if set) - Cannot be modified
• Deploy key (for imported repos) - Displayed for reference

​

Deleting projects

​

Delete workflow

1. Access project settings
   • Go to project settings
   • Scroll to “Danger Zone” section
2. Delete confirmation
   • Enter project name to confirm
   • Click “Delete Project” button
   • Confirm deletion in modal
3. Post-deletion
   • Project and all associated data are permanently removed
   • Cannot be undone
   • Repository data is deleted

​

Branch management

​

Understanding branches

Branches allow you to work on different versions of your cube definitions:

• Main/master branch - Production-ready cube definitions
• Feature branches - Development work for new features
• Environment branches - Different configurations for dev/staging/prod

​

Branch operations

Switch branches:

1. Click branch name in header
2. Select branch from dropdown
3. System automatically:
   • Loads files for selected branch
   • Updates Cube Playground
   • Refreshes API credentials

Create branch:

1. Click branch name in header
2. Click “Create Branch” option
3. Enter branch name
4. Select source branch to branch from
5. New branch is created and selected

Delete branch:

• Available in project settings
• Only non-protected branches can be deleted
• Cannot delete currently selected branch

​

Protected branches

Purpose:

• Prevent accidental changes to critical branches
• Enforce code review workflows
• Maintain production stability

Configuration:

• Set in project settings
• Specify branch names (e.g., main, master, production)
• Protected branches cannot be deleted or directly modified

​

Repository synchronization

​

Sync now

Manually pull latest changes from Git repository:

1. Click “Sync now” button in header
2. Wait for sync to complete
3. Changes reflected automatically:
   • Files are refreshed
   • Cube Playground reloads
   • API credentials update if needed

When to sync:

• After pushing changes from external Git client
• When collaborators make changes
• After merging pull requests
• To ensure you have latest schema definitions

​

Automatic sync

The system automatically:

• Syncs when switching projects
• Refreshes when switching branches
• Updates when project is first loaded

​

Project selection

​

Selecting active project

1. Click project name in header
2. Select project from dropdown menu
3. System automatically:
   • Switches to selected project
   • Starts heartbeat polling
   • Loads files and branches
   • Initializes Cube Playground

​

Project list

The dropdown shows:

• All available projects
• Project names
• Current project indicator
• “New project” option (if you have permissions)

​

Best practices

​

Project organization

​

Branch management

• Use descriptive branch names - feature/new-metrics, fix/revenue-calculation
• Protect critical branches - Always protect main/master branches
• Sync before switching - Ensure you have latest changes before switching branches
• Clean up unused branches - Delete branches that are no longer needed
• Review before merging - Use pull requests for protected branches

​

Repository selection

• Platform Managed - Best for new projects and quick setup
• Imported - Best for existing projects and team collaboration
• Consider team workflows - Choose based on your team’s Git practices

​

Troubleshooting

​

Common issues

---