-
Notifications
You must be signed in to change notification settings - Fork 52
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
No terraform plans have been published for this pipeline run. The terraform cli task must run plan with publishPlanResults: string (where string represents the plan name) to view plans. #9
Comments
@FernandoMiguel is this perhaps the same issue from charleszipp/azure-pipelines-tasks-terraform-old#255, charleszipp/azure-pipelines-tasks-terraform-old#275? is your azure devops org under a visualstudio.com address or self-hosted? Also can you capture the browser console to see if there are any errors when loading the tab? |
it's under https://dev.azure.com/ |
|
here's the plan payload
|
Just stumbled upon this myself. I also get 404 of the published plan. The strange thing is that it seems to work when I trigger the pipeline manually. Cannot say right now if it is because of the fact that, when I trigger manually, I get:
So, it could either be the trigger that is causing it, or the "contents" of the plan. |
Came across this issue recently too. It appears to relate to changes brought in with Terraform release 0.15.4, most likely relating to the new feature
From a quick scan of the source, I'd say the problem relates to the following: const planHasNoChangesRe = /^No changes. Infrastructure is up-to-date./ As Hashicorp appear to have changes the wording for when there are no changes from: |
I observed the same but I thought there is something other at fault. Each time I skip the stage apply because no changes has been detected the attachment gets into terraform-plan-results but the link actually doesn't work as the attachment is not uploaded. The plan can't be fetched on view and because of javascript as soon as plan can't be fetched everything on view fails and no plans are displayed. If it makes sense. |
Experiencing this issue too. @charleszipp : Any idea when this can be fixed? Judging from the input of @modwyer42 above, it would seem only this particular regex needs to be updated to account for the new output text? |
Hi, and first of all thanks for great tool, but I have same issue. |
I'm also running into this |
Hands down the best TF plugin. This is the only part not working. Would be great if someone could fix it. |
@jason-johnson any idea on when this might get fixed? Thanks for taking this project over... seems to be the best on the market so far. UPDATE: this is working, it only shows a plan when there are changes to be made. When it is a no change then nothing shows. I wish it would show regardless of change or not. Just so we could have a consistent pattern for business to review changes and go to a single location. Or at least when there is a "no change" plan to say that vs the "error" we get saying there was no published plan. |
I need to get my environment set up properly so I can test these things. Then, if it's as easy as it sounds then it should be fairly quick. So it could be within a month or less. |
There is a problem with the publish code. Imagine I have 3 stages in my pipeline which deploys to 3 different sites. When I provoke a change to the first run, then there will be a plan and a drop box to switch to the other plans. |
@yoogie27 can you confirm that you use a different string in |
Yes, I can confirm I was using a different string. |
Ok. We’ll try to reproduce that case as well. I think that’s a different case than this thread describes though, no? |
I believe this was fixed by #294. Please re-open if there is any new information here. |
Describe the bug
no plan view
To Reproduce
Steps to reproduce the behavior:
Expected behavior
to see plan view
Screenshots
Agent Configuration
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: