-
Notifications
You must be signed in to change notification settings - Fork 456
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
[k8s] update k8s client. #5210
[k8s] update k8s client. #5210
Conversation
@@ -84,7 +84,7 @@ public async void ReadDeploymentConfigFromSecret() | |||
}; | |||
|
|||
var client = new Mock<IKubernetes>(MockBehavior.Strict); | |||
client.Setup(c => c.ReadNamespacedSecretWithHttpMessagesAsync(DefaultSecretName, DefaultNamespace, It.IsAny<bool?>(), It.IsAny<bool?>(), null, null, It.IsAny<CancellationToken>())) | |||
client.Setup(c => c.ReadNamespacedSecretWithHttpMessagesAsync(DefaultSecretName, DefaultNamespace, It.IsAny<string>(), null, It.IsAny<CancellationToken>())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: since these are already being changed, should we put a named param for the null? Just to increase readability? Your call, not familiar with what the standard here is for our codebase, but just an idea :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if Moq will allow me to label these like name:DefaultSecretName
or if I should just comment them like I did elsewhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The quick attempt to label parameters gave me a compilation error, so I went with commenting the parameters like I did in the other files.
* Update to latest k8s client to address vulnerabilities in dependencies.
* Update to latest k8s client to address vulnerabilities in dependencies. (This project is not used in master, but it still referenced, so this needed to be updated to satisfy component governance.)
… (Azure#5483) * Update to latest k8s client to address vulnerabilities in dependencies. (This project is not used in master, but it still referenced, so this needed to be updated to satisfy component governance.)
Update to latest k8s client to address vulnerabilities in dependencies.