[mesheryctl] `registry` docs published under `exp` when command has been promoted already about meshery

[westcalcote]

I would like to help here, please.

[github-actions]

This issue has been labeled with 'component/mesheryctl'. Note that after making changes you need to update it in the mesheryctl command tracker spreadsheet.

---

        Be sure to join the community, if you haven't yet and please leave a ⭐ star on the project 😄

[leecalcote]

Thanks!

[leecalcote]

make docs-mesherctl is what you're looking for (largely).

[leecalcote]

@alphaX86 this issue persists despite some updates and this workflow running --> https://github.com/meshery/meshery/actions/runs/8163850432/job/22317958195#step:6:75

Do you know why make docs-mesheryctl (cd mesheryctl/docs; go run docs.go) doesn't pickup on the new location of registry?

[alphaX86]

@alphaX86 this issue persists despite some updates and this workflow running --> meshery/meshery/actions/runs/8163850432/job/22317958195#step:6:75

Do you know why make docs-mesheryctl (cd mesheryctl/docs; go run docs.go) doesn't pickup on the new location of registry?

I just need to look at the docs script behavior to find the cause. I'll take this up now and fix this.

[alphaX86]

From the trial run I conducted in local, my observation is they are already made and present in the docs/pages/reference/mesheryctl path. Screenshot is attached below...

So, right now, the script is not causing issue. The issue is with the reference table we have which needs manual update often. I'll update this for now.