Component slugs with config-as-code

[Keith Furnell]

Component slugs are not presented in generated compass.yml, but are also not available to be edited once a component is "Managed in compass.yml"

Are slugs that are set before switching to config-as-code, and not added in compass.yml, lost?

[April G · Accepted solution]

Hi Keith, thanks for your question. I checked this out, and it does look like a component slug set in the UI will be overwritten if it is later synced with a config that does not have a slug present.

I will be working on a bug fix to add the component slug to the generated compass.yml. In the meantime, you can set the same slug in the compass.yml to prevent any data loss:

slug: my-component-slug

[April G]

As an update, I pushed a fix that will populate the generated compass.yml with the component slug, if the component has one. That will prevent any data loss when onboarding to config-as-code. Thanks for surfacing this!