-
Notifications
You must be signed in to change notification settings - Fork 70
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
Image Automation not providing error message when git-repo has no write-access #102
Comments
I had the same issue in discussion #876 (seems github does not link discussions to issues so just adding that here for reference :-)). |
The response given by gitlab is:
$ flux get image update
NAME READY MESSAGE LAST RUN SUSPENDED
my-app-auto False remote: False
remote: ========================================================================
remote:
remote: This deploy key does not have write access to this project.
remote:
remote: ========================================================================
remote: Which is much better in that it gets the message across, but upsets the table layout somewhat. I can make a PR upstream in go-git, but either way I think the least brittle remedy is to anticipate that exact situation when using git operations, and replace it with a message that at least mentions what was being attempted. |
Are #115 active? Because having the same issue here with flux v2.0.0-rc.3
|
I have same issue @RogerSik using |
@ChrisJBurns fyi because this issue is closed I created a new one #548 |
We use an ssh-deploy key to have flux talk to repos (we use gitlab.com)
When we don't enable write-access on the git-repo for the deploy-key, flux (correctly) fails to write the image updates, but does not provide a nice error message as to why.
We get the following: (this is also output when using
flux get image update
)The text was updated successfully, but these errors were encountered: