Python: Add e2e test for strategic merge patch

Created on 10 Sep 2019 · 8Comments · Source: kubernetes-client/python

Add a test sending (e.g. config map) patches through the same API using:

JSON patch
Strategic merge patch

make sure the API client is able to set the content type properly according to the request body, and the patches are applied successfully.

ref: https://github.com/kubernetes-client/python/pull/931#discussion_r314435505

good first issue help wanted kinfeature lifecyclstale

Source

roycaihw

Most helpful comment

I want to give a shot at this. :)

/assign

palnabarun on 6 Oct 2019

👍2

All 8 comments

I want to give a shot at this. :)

/assign

palnabarun on 6 Oct 2019

👍2

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 4 Jan 2020

/remove-lifecycle stale

palnabarun on 5 Jan 2020

Examples of using these patches:

strategic merge patch: https://github.com/kubernetes-client/python/issues/641#issuecomment-429473349
json patch: https://github.com/kubernetes-client/python/issues/641#issuecomment-468291235

We can have one test sending multiple kinds of patch and make sure nothing fails, or two tests doing the same thing but using different kinds of patch.

roycaihw on 12 Mar 2020

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 10 Jun 2020

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 10 Jul 2020

this issue is marked as good for beginners, but seems old. can I still help as my first issue?

aliakbar-hemmati on 7 Oct 2020

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 5 Jan 2021

Was this page helpful?

0 / 5 - 0 ratings