Will config-as-code ever be complete?

[Keith Furnell]

A year ago I observed that neither component Details nor Documents can be managed through config-as-code:

https://community.atlassian.com/forums/Compass-questions/config-as-code-practicalities/qaq-p/2970693

The latter is particularly insidious as a component's Config-as-code page will include document DOCUMENT links in its generated compass.yml, but edits or additions to them are not synced.

Since then vertical dependencies have been also been added without config-as-code support. The comment thread from that announcement makes clear the community sentiment toward incomplete config-as-code implementation. Promised updates to documentation don't appear to have materialised. Is there actually a plan to fill this glaring gap in Compass's usability?

[Tinker Fadoua]

@Keith Furnell I will request Atlassian's assistance since your question is related to their product updates roadmap. 

All the best.

[Connor]

With Atlassian's recent Compass EOL announcement I assume the answer is no, or yes but only in Compass's replacement DX.

• https://www.atlassian.com/blog/announcements/the-next-chapter-for-compass 
• https://support.atlassian.com/compass/docs/migrate-from-compass-to-dx/#Feature-comparison--Compass-and-DX-Fabric 

[Tomislav Tobijas]

Curious if there have been any developments here since this was posted? Would be great to know if there’s been any progress. 👀

Has anyone tried reaching out to Atlassian Support to see what they have to say?