-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command print-tasks
does not generate yaml nor directory
#464
Comments
print-task
does not generate yaml nor directoryprint-tasks
does not generate yaml nor directory
Kinda missed this warning:
So this simplified the issue a lot. But is there a way to to run print-tasks when adding a new account? |
@mgamsjager did you ever figure it out? This would be very helpful to reviewing changes in generated CF templates. |
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 |
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#7053but using an older image also resulted in the same outcome.
Your environment
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.
The text was updated successfully, but these errors were encountered: