IntOrString type broke in 0.16.2

[pascal-cloudnatix]

Describe the bug
It seems that in the latest tag 0.16.2 intOrString type is broken again. In the 0.16.1 tag the IntOrString type was fixed.
Related issues:

• V1ServicePort with wrong type for targetPort #666
• PodDisruptionBudget types are incorrect #675

Seems like this commit 1f79306 undid the work done in this commit d44fa64

** Client Version **
0.16.2

To Reproduce

1. Install version 0.16.1 and check file @kubernetes/client-node/dist/gen/model/v1PodDisruptionBudgetSpec.d.ts
   V1PodDisruptionBudgetSpec should look like this:

export declare class V1PodDisruptionBudgetSpec {
    'maxUnavailable'?: IntOrString;
    'minAvailable'?: IntOrString;
}

2. Install version 0.16.2 and check file @kubernetes/client-node/dist/gen/model/v1PodDisruptionBudgetSpec.d.ts
   V1PodDisruptionBudgetSpec now looks like this, which removes the fixed type in 0.16.1

export declare class V1PodDisruptionBudgetSpec {
    'maxUnavailable'?: object;
    'minAvailable'?: object;
}

Expected behavior
Generated type should be:

export declare class V1PodDisruptionBudgetSpec {
    'maxUnavailable'?: IntOrString;
    'minAvailable'?: IntOrString;
}

Environment (please complete the following information):

• OS: MacOs
• NodeJS Version 16

[brendandburns]

Weird, not sure what happened here, but I will fix it.

[brendandburns]

Ok, apologies for the delay. It looks like when the 0.16.1 was generated the settings file changes were not checked in.

#774 has that fix and the fixed generated code too.

[brendandburns]

@pascal-cloudnatix once that PR is merged, I will cut an 0.16.3 release. If you could give it a quick review that will speed things up.

Thanks!

[brendandburns]

0.16.3 has been pushed out to NPM.

[pascal-cloudnatix]

Thanks so much Brendan 🙏