Need to modify parameters about c HOT 19 CLOSED

Good suggestion! I want to do this before but consider it as low priority.
And welcome PR, the change should be done in the openapi-generator project.

from c.

Ok. Thank U I will PR to openapi-generator project.

from c.

Hi @minerba

Do you have interest to fix this issue ?

The steps:

1. Update the files in the directory: https://github.com/OpenAPITools/openapi-generator/tree/master/modules/openapi-generator/src/main/resources/C-libcurl
2. Execute the script in https://github.com/kubernetes-client/gen with the configuration https://github.com/kubernetes-client/c/blob/master/settings to get a generated directory kubernetes

• The step 2 can be replaced with below commands if you want to use the current swagger spec of Kubernetes API server:

# Execute the command in the directory of repo `OpenAPITools/openapi-generator`
mvn clean package
java -jar modules/openapi-generator-cli/target/openapi-generator-cli.jar generate -i ../c/kubernetes/swagger.json   -g c    -o ../kubernetes --skip-validate-spec

3. Copy the files in kubernetes to overwrite the files in the directory of this repo c/kubernetes/ except CMakeLists.txt
4. Follow the https://github.com/kubernetes-client/c/blob/master/README.md to build and test
5. Create a PR to apply to merge.

from c.

I will fix it. Reopen this ticket to trace.

from c.

Could you please give any function for example ?

from c.

I have a Compile warning in this function

Because of parameters "char *" .

v1_pod_t* CoreV1API_readNamespacedPod(apiClient_t *apiClient, char * name , char * _namespace , char * pretty , int exact , int _export )

parameters name, _namespace, pretty are unlikely to be modified.

I suggest that functions that take a parameter "char " are changed to "const char"

The same for other functions in Directory '/kubernetes/api/*'.

from c.

@minerba

You need submit 2 PR.

• The 1st PR is in OpenAPI-Generator, take this PR OpenAPITools/openapi-generator#10034 as example
• The 2nd PR will be here. FYI #68

from c.

Hi @minerba

Are you still working on this ticket ?

from c.

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

from c.

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

from c.

/remove-lifecycle rotten

from c.

@ityuhui
sorry Well... How can I apply this command? "/remove-lifecycle rotten"

from c.

How can I apply this command? "/remove-lifecycle rotten"

I have done it. You don't need do it again.

from c.

@ityuhui Thank you:)

from c.

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

from c.

Thanks your Pr.

from c.

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

from c.

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

from c.

@k8s-triage-robot: Closing this issue.

from c.