Yup - it can be pretty overwhelming, it depends on what it detected on your system! The state.json will usually explain why it 'harvested' something (perhaps it was because it found a running systemd service, perhaps it was due to detecting a package having been manually installed, etc)

There is the --exclude option which might help (also keep in mind you can define an enroll.ini file to manage the flags so it's less cumbersome). Otherwise, you can always prune the roles from the ansible dir/playbook.

I'm going to continue to work on easy options to skip stuff. In particular I do think many of the 'lib' packages could be omitted if they are just dependencies of other packages already detected as part of the harvest. (Need to basically build a dependency graph)

Thanks for trying it out!

▲

mlrtime 5 days ago | parent | next [-]

Can you create a baseline system to create the ignores?

What I mean is in some large companies you are given a host that already has lots of config changes, possibly by ansible. Then your team has to configure on top of those changes, maybe ansible again. I'd like to run on the baseline system given to create a baseline, then on a production host to see how it drifted.

Sorry if this is in the docs, cool tool!

	▲	_mig5 5 days ago \| parent [-]
		Hi mlrtime. You could run it on a base system, and use --exclude-path and --include-path all you want, to capture or ignore the things you don't care about. Treat that as your 'golden' harvest state. You could then run a 'harvest' on the production system. You'd then be able to run 'enroll diff --old baseline --new production' to compare the difference. You could also first run the manifest of the baseline harvest against your production, to ensure it has (at least) all the same things as the baseline. A 'harvest' of production after that, would probably then show just stuff that existed on production already that wasn't in the baseline. I hope that makes sense!

▲

gerdesj 5 days ago | parent | prev [-]

I've just run it against my desktop PC.

I had documented everything up to a point on this beatie and then things have got out of hand. I now have all the changes from after I went off piste.

What a great tool.

Thank you.