Closed MoChilia closed 4 months ago
I'm not sure what happened here, but this fix does not work for me. It almost looks as if something got cached? I have no clue how the same python error can appear here if curl was eliminated? Is there any other instance of curl somewhere?
Hi @jakub-lesniak-ikea, does it work for you with v2
tag?
Hi @jakub-lesniak-ikea, does it work for you with
v2
tag?
No it does not, that was the reason I started testing the fix-153
. It somehow looks like the error that I am getting might not be related to the action at all. I just tested with simple bash action that utilises the CLI installed on the agent and got the same error - which suggests that it might be coming from the CLI itself.
@MoChilia can you tell me/us what the process and requirements are for approval to merge this? Do we still have to do something?
@luc122c, @MeikeMertschFortum, @jakub-lesniak-ikea, it has now been merged into master
. You can point to master
as a temporary workaround. I will inform you once the new version is released.
Thank you for your help
Fix the issue #153, replace
curl
with aGET
request to prevent stdout cutoff in Azure CLI versions, avoiding warnings in workflows.Close #153