isMonorepoProject setting in compass.yml results in sync error when present
Whenever I include `isMonorepoProject` in my `compass.yml` file, the following error message appears in the UI after pushing the change:
"isMonorepoProject" must be one of the following keys: tier, lifecycle
The relevant section of `compass.yml` is formatted as follows:
fields:
tier: 2
lifecycle: Active
isMonorepoProject: true
The current docs indicate that that is how it should be structured. I have several compass files, each in its own subfolder as instructed. So, I'm at a loss to understand the problem with my implementation. Has anyone else had this issue?
1 answer
1 accepted
Hi, @John Homenuke !
The excerpt that you're suggesting seems okay at first blush - you can always compare it with the YAML generated for a manually-created component using the same configuration in the "Config as code" left side tab of an individual Component page.
I just tested this with a Bitbucket and a GitHub repository and the config as code syncing completed as expected.
If you're using one of these Forge apps to integrate with a repository, have you checked that is up-to-date and using the latest version? Support for this field was only added to the most recent ones. You can verify this in Apps > Manage your apps and then checking the details for the SCM integration that you are currently using. If an update were there pending confirmation, you would see it as an "Upgrade" button.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.