| Hi Oana Tanasoiu this doesn't seem to be working as expected. Using puppet 7.3.0, the --no-legacy option is rejected:
$ git rev-parse HEAD |
3d4df020ea74ca5695e03229fa1279adf0dda3fa |
$ bx puppet facts show --no-legacy | jq . |
Error: Could not parse application options: invalid option: --no-legacy
|
It looks like https://github.com/puppetlabs/puppet/pull/8475 was merged first in https://github.com/puppetlabs/puppet/commit/49918bd5cc17a93bba14d2b9a94b44848fdb7b4d which added --no-legacy, but it accidentally removed --show-legacy. The change to --show-legacy broke other applications that call puppet facts show. So https://github.com/puppetlabs/puppet/pull/8478 restored --show-legacy and that was merged in https://github.com/puppetlabs/puppet/commit/a600c40f32cfbcf77d58ae19f62ff5710a7fe940. Using that version --show-legacy and --no-legacy are both accepted, but the latter doesn't omit legacy facts:
$ bx puppet facts show | jq .virtual |
"physical" |
$ bx puppet facts show --no-legacy | jq .virtual |
"physical"
|
Then https://github.com/puppetlabs/puppet/pull/8482 was merged, which removed the ability to specify --no-legacy. So aren't we back where we started and this ticket isn't fixed? |