Configuration as Code allows your CloudBees Feature Management configuration to be stored as source code.
CasC integrates CloudBees Feature Management with your existing environment.
This approach offers the following benefits:
-
Simplified deployment using pull requests for testing and release.
-
Version control to track and roll back changes.
-
Feature delivery integration into deployment and release pipelines.
-
You can add tools like automated testing to update target groups and flag configurations based on production data.
-
-
Supports copying definitions between environments.
-
This can be performed using a pull request to create a new branch that can be merged into the development branch.
-
-
Microservices-oriented development and testing for simplified control over flag behavior in a non-production environment.
-
Refer to Microservices automated testing and local development for more information.
-
To learn more about how CloudBees Feature Management is protected from outages and reduces latency, refer to Resiliency.
Activating CasC
CasC is activated by connecting to your source code repository.
The CloudBees Feature Management integration with your code repository is bidirectional. Changes made to your Git source code cause CloudBees Feature Management to be updated and vice versa.
If you make changes in your repository and push it to the remote origin branch, CloudBees Feature Management will pick these updates and update the dashboard accordingly. If you make changes in the dashboard, CloudBees Feature Management will push commits to your repository.
Refer to Activating CasC with GitHub for more information.