---
title: "Feature Flags and GitOps"
chapter: false
weight: 5
--- 

### Connecting to GitHub Cloud
1. Create an empty repository named ***feature-flags-configuration-as-code*** in your workshop GitHub Organization. 
2. Connect the CloudBees Feature Management app into the Github repository by:
  - Going to **App Settings > Integrations tab** (from the left Panel) in the CloudBees Feature Management dashboard.
  - Click the **Connect** button in the **GitHub** panel. ![GitHub App](app-integrations.png?width=50pc)
3. In GitHub, select your workshop GitHub Organization to integrate with CloudBees Feature Management GitHub app. On the next screen select the ***Only select repositories*** and then select the feature-flags-configuration-as-code repository you just created. ![GitHub App](github-app-repo.png?width=50pc)
4. After clicking the **Install** button you will be redirected back to the CloudBees Feature Management dashboard to select your app and the repository you just created. ![GitHub App](github-rollout-confirmation.png?width=50pc) 
5. Click **Connect** and you are done integrating CloudBees Feature Management with GitHub. ![Connected](connected.png?width=50pc) 

### Using CasC and GitOps
1. In the CloudBees Feature Management dashboard, disable the sidebar experiment in Development environment by toggling targeting from On to Off. ![Connected](sidebar_killed.png?width=50pc)
2. In GitHub, navigate to your feature-flags-configuration-as-code repository and note the structure. You should see an automatically generated README.md and a target_groups directory.
3. Switch from master branch to the automatically created Development branch and note the differences. Note the existence of an experiments folder that contains default.sidebar.yml with enabled: false on line 3.
4. Within the GitHub code editor, modify default.sidebar.yml by editing the line enabled: false to become enabled: true and commit to Development branch. Your YAML should closely resemble this:

```YAML
type: experiment
name: sidebar
flag: default.sidebar
enabled: true
conditions:
  		- group:
      			name: BetaUsers
    			value: true
		value: false
```
5. In the CloudBees Feature Management dashboard, notice that your **default.sidebar** configuration has been reactivated in the **Development** environment.
6. Now that you are satisfied with the configuration in your Development environment, you want to include this experiment in your Production environment. In Github, merge the Development branch to main branch by creating and merging a pull request. Make sure not to delete the Development branch after confirming the merge.
7. In CloudBees Feature Management dashboard, note the **sidebar** and **title** experiments have now added to your **Production** environment. ![Connected](production_sidebar.png?width=50pc)

### Lab 5 Completed!
Congratulations! You have finished the fifth and final lab!