The DX Engineering Intelligence Platform is our latest solution in tracking developer productivity & experience, measuring AI impact, and understanding overall software health. As we focus on delivering these next-generation IDP capabilities, Compass scorecards and catalog functionality will transition into DX. We encourage you to explore DX and discuss migration options with your account manager.

Learn more

Disconnect managed components from config as code

If you no longer want to manage a component with config as code, you can disconnect it from the repository. After you disconnect it, the component retains the most recent details from the compass.yml file and becomes unmanaged. You can edit its details from the Compass UI.

Before you begin

Verify that you can access the workspace/organization configured for Compass and you have permissions to delete files from the repositories within that workspace/organization.
You’ll also need some basic experience with using Git and Bitbucket Cloud or GitHub.

Disconnect a managed component from config as code

To disconnect a managed component from config as code:

Go to the location of the compass.yml file in the source repository and delete the file.
Push the changes and open a pull request if necessary.
Merge the changes to your repository’s default branch.
- The component is no longer managed with config as code.
Verify that there's not a link under the component name that says Managed by config as code in {name of source code provider}. There should no longer be a link or any subtext.

The component is now disconnected from config as code.

You can update its details from the Compass UI. Alternatively, you can start managing it again with config as code at any time. Learn how to manage components via config as code