Manifest catalogs view doesn't reflect the array order

[timsutton]

Just leaving this here to raise an issue I ran into this morning. I rarely use MunkiAdmin for manifest editing, so please excuse if i'm missing an option or a known workaround for this.

I had a group manifest for which I wanted to add a new catalog to all of its members, so I could offer a newer version of an app than what is in my most-commonly-used production catalog. I added the new catalog (ea-studios) to the app, rebuilt catalogs, and reloaded MunkiAdmin's catalog state so that it would display the new catalog in the catalogs list for the individual manifests' views. I checked off the catalog item to add it to the manifest, and saved it.

When I saw the client was still not getting the newer version of the app available, however, it was only once I looked at the manifest plist directly that I immediately saw the issue, which is that had appended ea-studios to the end of the array, whereas I would normally have added it to the beginning to ensure that the clients found that version first before "settling" on what was available in production.

It just occurred to me the UI for the catalogs view hides this functional detail from the admin, which can be an issue if you're making use of this design pattern in Munki. I suppose that if the catalogs view was a list which could be reordered, then configuring exactly the right order could be set.

[hjuutilainen]

It could be presented more clearly but you should already be able to drag and reorder the catalogs in the current version.

[timsutton]

Aha, so it was user error! Thanks for clarifying that.