-
Notifications
You must be signed in to change notification settings - Fork 7
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
Error reading aws config on non-ephemeral runners #19
Comments
I guess we can delete the file as the last step in |
I could delete the file, but won't that mess up the ability to switch between profiles which is being added in #17? |
Not right now. We don't use that file as we push to env vars currently. If you check my last comment, we could try something like writing to I think, deleting the file before this action runs could maybe work but then deleting files on the runner feels like a risky move because we're modifying the environment and we're touching files created outside of this action (most likely those files were created by a previous run of this action but we can't be sure of that). Apart from those, do you have any other ideas about tackling this? |
Could we use the |
Sure. That would be limited to home folder and contingent upon the fact that writing to |
Link to PR: #20 |
I'm having a problem similar to #17
We're using self hosted runner which are not (unfortunately) ephemeral. I'm getting an error when running this action on a runner that has run this action in the past. Since this action is appending instead of replacing, subsequent runs have duplicates in their files. I can solve this on my end by running
rm -f $HOME/actions-runner/_work/_temp/_github_home/.aws/config
before using this action, but it would be nice to not have to worry about that.Here's the error:
The text was updated successfully, but these errors were encountered: