add catalog source to list verb output

[Coros]

Please add the catalog source for discovered installers so we can identify what is a public release or a beta. Another option would be to add an argument to only list from a specified (public, customer beta, dev beta) catalog.

[ninxsoft]

Betas builds generally end in a lower case string, for example:

Version	Build
macOS Monterey 12.2.1	21D62
macOS Monterey 12.3 Beta 2	21E5206e
macOS Big Sur 11.6.3	20G415

Catalogs are specific to macOS Installers (.app), as I am sourcing firmware downloads via this JSON file. I think it makes more sense to add a column indicating if a build is beta or not, if this is something you require?

Thoughts?

[ninxsoft]

Almost forgot, you can use the -c / --catalog-url flag to specify a catalog.

You can also use the -b / --include-betas flag to skip betas.

Does this solve your issue?

[Coros]

I'm unable to get -b / --include-betas to do anything. Essentially when Big Sur 11.6.3 was first released as a beta, it appeared in the list and had a normal looking build version. Due to the way it was listed, I thought it was a full release. I was hoping to prevent that mistake again.

[ninxsoft]

I am getting the following output when running mist list --include-betas:

➜ ~ mist list --include-betas
┌──────────────────┐
│ INPUT VALIDATION │
└──────────────────┘
  ├─ Platform will be 'intel'...
  ├─ Include betas in search results will be 'true'...
  ├─ Output type will be 'ascii'...
┌────────┐
│ SEARCH │
└────────┘
  ├─ Searching for macOS Installer versions...
  └─ Found 23 macOS Installer(s) available for download

Identifier │ Name                   │ Version │ Build    │ Size     │ Date      
───────────┼────────────────────────┼─────────┼──────────┼──────────┼───────────
002-66217  │ macOS Monterey beta    │ 12.3    │ 21E5206e │ 12.14 GB │ 2022-02-10
002-66265  │ macOS Monterey         │ 12.2.1  │ 21D62    │ 12.16 GB │ 2022-02-11
002-57041  │ macOS Monterey         │ 12.2    │ 21D49    │ 12.16 GB │ 2022-01-27
002-42435  │ macOS Monterey         │ 12.1    │ 21C52    │ 12.16 GB │ 2022-01-15
002-23774  │ macOS Monterey         │ 12.0.1  │ 21A559   │ 12.13 GB │ 2021-12-02
002-65695  │ macOS Big Sur          │ 11.6.4  │ 20G417   │ 12.45 GB │ 2022-02-15
002-57023  │ macOS Big Sur          │ 11.6.3  │ 20G415   │ 12.44 GB │ 2022-01-27
002-42341  │ macOS Big Sur          │ 11.6.2  │ 20G314   │ 12.44 GB │ 2022-01-15
002-23589  │ macOS Big Sur          │ 11.6.1  │ 20G224   │ 12.43 GB │ 2021-12-02
071-78704  │ macOS Big Sur          │ 11.5.2  │ 20G95    │ 12.45 GB │ 2021-08-19
001-68446  │ macOS Catalina         │ 10.15.7 │ 19H15    │ 08.75 GB │ 2020-11-12
001-57224  │ macOS Catalina         │ 10.15.7 │ 19H4     │ 08.75 GB │ 2020-10-28
001-51042  │ macOS Catalina         │ 10.15.7 │ 19H2     │ 08.75 GB │ 2020-09-25
001-36801  │ macOS Catalina         │ 10.15.6 │ 19G2021  │ 08.75 GB │ 2020-08-13
001-36735  │ macOS Catalina         │ 10.15.6 │ 19G2006  │ 08.75 GB │ 2020-08-07
001-15219  │ macOS Catalina         │ 10.15.5 │ 19F2200  │ 08.74 GB │ 2020-06-16
001-04366  │ macOS Catalina         │ 10.15.4 │ 19E2269  │ 08.75 GB │ 2020-05-05
061-86291  │ macOS Catalina         │ 10.15.3 │ 19D2064  │ 08.69 GB │ 2020-03-24
061-26589  │ macOS Mojave           │ 10.14.6 │ 18G103   │ 06.52 GB │ 2019-10-15
061-26578  │ macOS Mojave           │ 10.14.5 │ 18F2059  │ 06.52 GB │ 2019-10-15
041-88800  │ macOS Mojave           │ 10.14.4 │ 18E2034  │ 06.53 GB │ 2019-10-24
041-91758  │ macOS High Sierra      │ 10.13.6 │ 17G66    │ 05.71 GB │ 2019-10-20
041-90855  │ macOS High Sierra Beta │ 10.13.5 │ 17F66a   │ 05.69 GB │ 2019-10-24

The builds do show up with a lowercase suffix, indicating beta builds.

Note: This is entirely dependent on what data is provided by the catalog(s).

Adding a 'beta' key to the ASCII / CSV / JSON / PLIST / YAML output will still use the same data provided by the catalog to determine if the installer is a beta (ie. lowercase suffix).

[ninxsoft]

@Coros do you happen to recall the macOS Big Sur build number that was potentially a beta?

[PicoMitchell]

This sounds like they may have seen an RC build which didn't have a beta suffix and would have had a very close to final or exact same as final build number.

The issue of RCs appearing as if they are final/production builds is why I requested the --include-betas flag to be added and for betas for not be included by default.

@Coros Were you possibly still running mist 1.5 or older when you saw this beta/RC in the default list? I think this shouldn't have been an issue on mist 1.6 or newer.

[ninxsoft]

Closing due to inactivity, will re-open if required.