where does "cs_tools tools scriptability export" write the logs in v1.6.2?

[bmofkn]

We just upgraded from v1.5.x to v1.6.2.
We use commands like the following:
cs_tools tools scriptability export --directory ./ --metadata-types SQL_VIEW --include-system --config prod_ts

In v1.5.x, logs were written to ./logs/export-YYYY.MM.DD-HH.MM.SS. It's not apparent where these logs are written in v1.6.2.

I'm sure I'm just overlooking the obvious 🤪. Any help is greatly appreciated.

[boonhapus]

@bmofkn All the logs are centralized now, we no longer redirect the scriptability lines to a separate file.

cs_tools self info will show you the directory which holds your config, the logs are in a hidden directory there as well (.logs).

If you use --log-errors or run this tool in CI, all of the statuses should print to screen, and in 1.6.2 specifically the OS exit code should be 0 for success, 1 for any error, and 2 for any warning.

[bmofkn]

@boonhapus, good to know. We were keeping these logs in a local git repo that synced with OneDrive... used them for auditing success and failure. For v1.6.2+, we added a line to the end our script file:

cs_tools logs report ./csToolsLogs --latest 7

This gives us the logs for the last seven scripts (which are based on seven metadata-types). All good now 🙂

[boonhapus]

Makes sense @bmofkn . Also check out the guide on scriptability as well. It may help simplify some of your patterns with this version.

There's some examples of git local at the bottom that worked for me -- but I'm a git gui snob and had to have my buddy Claude me suffer through bash scripting to get it working, so YMMV 😅