a regression issue caused by fix #160

[Liu, Yabing]

Take "CoreV1API_patchNodeStatus"as an example:
fix #160 (#160) appends "force=0" to Patch HTTP Request. Then we will get an Error in the response as below.

"causes": [
    {
        "reason": "FieldValueForbidden",
        "message":"Forbidden: may not be specified for non-apply patch","field":"force"
    }
]

[Hui Yu]

Thanks for reporting this issue. It's hard to get a solution because we don't want int * as the datatype of the parameter. Do you have any advice?

[Kubernetes Triage Robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Kubernetes Triage Robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[Hui Yu]

/remove-lifecycle rotten

[Hui Yu]

Resovled by #210