-
Notifications
You must be signed in to change notification settings - Fork 34
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
FIXME: Remove go mod tidy && go mod vendor
once we find the reason why ci workflow fails without it.
#384
Comments
nixpanic
added a commit
to nixpanic/kubernetes-csi-addons
that referenced
this issue
Jun 28, 2023
There has been a bad proxy somewhere that caused issues downloading or verfying the github.com/operator-framework/operator-sdk module. Things have recovered now, so the extra tidy/vendor commands are not needed anymore. Closes: csi-addons#384 Signed-off-by: Niels de Vos <ndevos@ibm.com>
nixpanic
added a commit
to nixpanic/kubernetes-csi-addons
that referenced
this issue
Aug 22, 2023
There has been a bad proxy somewhere that caused issues downloading or verfying the github.com/operator-framework/operator-sdk module. Things have recovered now, so the extra tidy/vendor commands are not needed anymore. Closes: csi-addons#384 Signed-off-by: Niels de Vos <ndevos@ibm.com>
nixpanic
added a commit
to nixpanic/kubernetes-csi-addons
that referenced
this issue
Oct 12, 2023
There has been a bad proxy somewhere that caused issues downloading or verfying the github.com/operator-framework/operator-sdk module. Things have recovered now, so the extra tidy/vendor commands are not needed anymore. Closes: csi-addons#384 Signed-off-by: Niels de Vos <ndevos@ibm.com>
nixpanic
added a commit
to nixpanic/kubernetes-csi-addons
that referenced
this issue
Oct 31, 2023
There has been a bad proxy somewhere that caused issues downloading or verfying the github.com/operator-framework/operator-sdk module. Things have recovered now, so the extra tidy/vendor commands are not needed anymore. Closes: csi-addons#384 Signed-off-by: Niels de Vos <ndevos@ibm.com>
Madhu-1
pushed a commit
to nixpanic/kubernetes-csi-addons
that referenced
this issue
Nov 9, 2023
There has been a bad proxy somewhere that caused issues downloading or verfying the github.com/operator-framework/operator-sdk module. Things have recovered now, so the extra tidy/vendor commands are not needed anymore. Closes: csi-addons#384 Signed-off-by: Niels de Vos <ndevos@ibm.com>
nixpanic
added a commit
to nixpanic/kubernetes-csi-addons
that referenced
this issue
Dec 12, 2023
There has been a bad proxy somewhere that caused issues downloading or verfying the github.com/operator-framework/operator-sdk module. Things have recovered now, so the extra tidy/vendor commands are not needed anymore. Closes: csi-addons#384 Signed-off-by: Niels de Vos <ndevos@ibm.com>
nixpanic
added a commit
to nixpanic/kubernetes-csi-addons
that referenced
this issue
Dec 12, 2023
There has been a bad proxy somewhere that caused issues downloading or verfying the github.com/operator-framework/operator-sdk module. Things have recovered now, so the extra tidy/vendor commands are not needed anymore. Closes: csi-addons#384 Signed-off-by: Niels de Vos <ndevos@ibm.com>
nixpanic
added a commit
to nixpanic/kubernetes-csi-addons
that referenced
this issue
Jan 4, 2024
There has been a bad proxy somewhere that caused issues downloading or verfying the github.com/operator-framework/operator-sdk module. Things have recovered now, so the extra tidy/vendor commands are not needed anymore. Closes: csi-addons#384 Signed-off-by: Niels de Vos <ndevos@ibm.com>
nixpanic
added a commit
to nixpanic/kubernetes-csi-addons
that referenced
this issue
Jan 4, 2024
There has been a bad proxy somewhere that caused issues downloading or verfying the github.com/operator-framework/operator-sdk module. Things have recovered now, so the extra tidy/vendor commands are not needed anymore. Closes: csi-addons#384 Signed-off-by: Niels de Vos <ndevos@ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
refer: #382
The text was updated successfully, but these errors were encountered: