Command print-tasks does not generate yaml nor directory

[mgamsjager]

Subject of the issue

Today I saw that on one of our customers CI that the print-tasks command no longer generates the ./.printed-stacks/ folder nor generates any data at all. The command exits successfully.
The issue is reproducible locally on OSX and on Github with all current ubuntu images.
Other customer with Gitlab and a very old nodejs version (10.x) does not have the same issue.

Org-formation versions are all the same.

5 days ago it did work (with https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20230129.2) which lead me to believe it had to do with actions/runner-images#7053
but using an older image also resulted in the same outcome.

Your environment

• version of org-foramtion: 1.0.7
• version of node: 16.19.0
• which OS/distro: Ubuntu latest, 22.04

Steps to reproduce

$ org-formation print-tasks ./organization-tasks.yml
$ ls -al ./.printed-stacks/
-> ls: ./.printed-stacks/: No such file or directory

Expected behaviour

Generate the print-stack (used by static code tool)

Actual behaviour

print-tasks exits successfully but no files are being generated.

[mgamsjager]

Kinda missed this warning:

WARN: Accounts were added to the organization model.
WARN: Tasks might depend on updating the organization.
WARN: Validation and printing of tasks will be skipped.

So this simplified the issue a lot. But is there a way to to run print-tasks when adding a new account?

[OperationalFallacy]

@mgamsjager did you ever figure it out? This would be very helpful to reviewing changes in generated CF templates.

[OlafConijn]

i think the "issue" is that print-tasks cannot print task if there were accounts added to your organization. after you have performed tasks (updated the organization + state) it will be able to print tasks.

not sure whether this is of importance to your usecase @OperationalFallacy