[CT-1759] dbt parse should (over)write manifest.json by default

[jtcohen6]

That's it, that's the issue.

dbt-core/core/dbt/task/parse.py

Lines 97 to 99 in d43c070

	if self.args.write_manifest:
	fire_event(ParseCmdWritingManifest())
	self.write_manifest()

I find it mildly annoying that I can't use just dbt parse, when all I want to do is update manifest.json with the latest project contents, often for manual inspection / debugging.

We can make this opt-out (with a --no-write-manifest argument), instead of opt-in (with a --write-manifest flag as it is today).

[gshank]

@jtcohen6 In my protobuf nodes branch I added a bit to write out the manifest.json when we write out the partial parse manifest. I hadn't thought about the implications for the "parse" command, but that change would have made the '--write-manifest' flag a no-op. (as a side note, when I wrote the parse command I wanted to write out the manifest.json but was overruled, so the --write-manifest thing was a compromise). I could pull that change out of the protobuf nodes branch if we want to move that bit up...

[jtcohen6]

as a side note, when I wrote the parse command I wanted to write out the manifest.json but was overruled, so the --write-manifest thing was a compromise

overruled! by me?? quite possibly

I could pull that change out of the protobuf nodes branch if we want to move that bit up...

I'm just happy to have this change happen, I don't feel strongly that it must happen immediately

[jtcohen6]

Resolved by #6565