Skip to content
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

Merged
merged 3 commits into from
Jul 13, 2021
Merged

Conversation

darobs
Copy link
Contributor

@darobs darobs commented Jul 6, 2021

Update to latest k8s client to address vulnerabilities in dependencies.

@darobs darobs requested a review from dmolokanov July 8, 2021 01:02
@@ -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>()))
Copy link
Contributor

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 :)

Copy link
Contributor Author

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.

Copy link
Contributor Author

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.

@darobs darobs merged commit c55a5db into release/1.1-k8s-preview Jul 13, 2021
@darobs darobs deleted the darobs/k8s-client-update branch July 13, 2021 22:04
darobs added a commit that referenced this pull request Jul 14, 2021
* Update to latest k8s client to address vulnerabilities in dependencies.
kodiakhq bot pushed a commit that referenced this pull request Jul 19, 2021
Cherry-pick k8s change to 1.1.

* Update to latest k8s client to address vulnerabilities in dependencies.
darobs added a commit that referenced this pull request Aug 3, 2021
Cherry-pick k8s change 1.1->master

* Update to latest k8s client to address vulnerabilities in dependencies.
darobs added a commit that referenced this pull request Aug 3, 2021
Cherry-pick k8s change to 1.1->1.2

* Update to latest k8s client to address vulnerabilities in dependencies.
kodiakhq bot pushed a commit that referenced this pull request Aug 9, 2021
[k8s] update k8s client. (#5210) (#5250)
755e65f
Cherry-pick k8s change to 1.1->1.2

* Update to latest k8s client to address vulnerabilities in dependencies.

(This project is not used in 1.2, but it still referenced, so this needed to be updated to satisfy component governance.)
darobs added a commit to darobs/iotedge that referenced this pull request Sep 9, 2021
* 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.)
kodiakhq bot pushed a commit that referenced this pull request Sep 9, 2021
* 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.)
damonbarry pushed a commit to damonbarry/iotedge that referenced this pull request Apr 15, 2022
… (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.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants