You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a large batch of resources are created, but resources exited before running the program, then there will probably be a conflict at some point.
For example, consider that Tower already has project A, which does not have a helloworld.yml playbook. This program creates project B, which does have it. It then tries to create job templates with this playbook. At least one of those job templates will accidentally use project A, which will cause an error and halt the data creation half-way through.
This issue is to work around referencing projects that don't have the standard data format.
The text was updated successfully, but these errors were encountered:
If a large batch of resources are created, but resources exited before running the program, then there will probably be a conflict at some point.
For example, consider that Tower already has project A, which does not have a
helloworld.yml
playbook. This program creates project B, which does have it. It then tries to create job templates with this playbook. At least one of those job templates will accidentally use project A, which will cause an error and halt the data creation half-way through.This issue is to work around referencing projects that don't have the standard data format.
The text was updated successfully, but these errors were encountered: