Skip to content

TPI behaves differently in the CI #630

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.

Sign up for GitHub

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

Jump to bottom
Closed
casperdcl opened this issue Jul 28, 2022 · 0 comments · Fixed by #705
Closed

TPI behaves differently in the CI #630

casperdcl opened this issue Jul 28, 2022 · 0 comments · Fixed by #705
Assignees
@dacbd
Labels
discussion Waiting for team decision documentation Markdown files p1-important High priority resource-task iterative_task TF resource

Comments

@casperdcl
Copy link
Contributor

casperdcl commented Jul 28, 2022 •
edited
Loading

  • TPI workflows are restarted iff run in CI, but not if run locally (counter-intuitive)
  • This behaviour is not documented
  • The use case -- i.e. no need to have an explicit for-loop wrapping the refresh && iterative_task.example.status["succeeded"] -- doesn't seem enough justification
@casperdcl casperdcl added documentation Markdown files p1-important High priority discussion Waiting for team decision resource-task iterative_task TF resource labels Jul 28, 2022
This was referenced Jul 29, 2022
Open
Open
@dacbd dacbd mentioned this issue Oct 27, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dacbd dacbd

Labels
discussion Waiting for team decision documentation Markdown files p1-important High priority resource-task iterative_task TF resource
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove cml rerun-workflow iterative/terraform-provider-iterative
2 participants
@dacbd @casperdcl