Improve Docker context handling with update and existence check #12
Conversation
|
Thank you for the support. I had planned to work on this over the weekend but got busy. So I will review these PR's this week no later than this weekend. |
|
Thanks for your quick response. Let me know if there's anything that can be improved in this PR. |
|
I was actually able to reproduce this while working on the other PR. I have included this fix in that PR and will close this one once that PR is merged. For reference I added 2 stack deploys to the single test job to reproduce it. So this fix will allow deploying multiple stacks in a single job now. Thank you for having this problem solved for me =) |
|
I had to include this in my other PR to fix the https://github.com/cssnr/stack-deploy-action/releases/tag/v1.0.1 Thank you very much for the contribution and support. Please let me know if you run into any more issues... |
|
I appreciate your work, thank you. |
First, I want to thank you for the work you've put into this GitHub Action.
I encountered some issues with the creation of the Docker context on my self-hosted GitHub Actions runner. It seems like the context might be cached.
In my PR, I first check whether the context exists. If it doesn’t, a new one is created; otherwise, the remote context is updated.
To test this, I forked the repository into the repo where I wanted to use the action and referenced the path to the action in my repository. It worked for me.