Skip to content

[Examples] Incorrect Module Reference #252

Description

@codevulture

client-python/examples/create_thirdparty_resource.md
Shows:
from kubernetes.rest import ApiException
should be
from kubernetes.client.rest import ApiException
Kindly check.

Activity

  1. mbohlool commented on Jun 13, 2017

    @mbohlool
    Contributor

    Yes, all examples need to be updated. We should update example's template (and probably documentation templates) to match our client structure.

  2. wyjw commented on Jul 6, 2017

    @wyjw

    Could I be assigned this?

    I would go through and fix the module imports for all the examples.

    Could you please elaborate on what else needs to be changed about the template for the examples and the documentation? I could try to see what I can do.

  3. mbohlool commented on Jul 6, 2017

    @mbohlool
    Contributor

    Great, Fixing imports (and adding a config.load_kube_config) would be a great start. Just look at one of the examples in examples/ folder and make examples template look close to those. Now to fix templates, you need to copy them somewhere. We are moving toward using kubernetes-client/gen repo for all generations: #284

    I have a PR in that repo to move templates from swagger-codegen to gen repo for java client: kubernetes-client/gen#16

    you can follow the same pattern, copy templates and start changing them. Make sure you document the branch/sha key from which you copied templates. Don't do everything in one PR, send a PR for moving templates (and all changes necessary for them to work) first to make sure we are on the right path and then start sending PRs to fix example(s) template. Let me know if you had any questions.

  4. wyjw commented on Jul 7, 2017

    @wyjw

    Thanks for the pointers. Ok will do. I'll follow the examples for the java client and try to do something similar.

  5. mbohlool commented on Jul 7, 2017

    @mbohlool
    Contributor
  6. wyjw commented on Jul 16, 2017

    @wyjw

    I'm swamped with work unexpectedly and unfortunately. If anyone else wants to take this, go for it. Sorry.

  7. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 30, 2018
  8. iamneha commented on Oct 31, 2018

    @iamneha
    Contributor

    /assign @iamneha

  9. k8s-ci-robot commented on Oct 31, 2018

    @k8s-ci-robot
    Contributor

    @iamneha: GitHub didn't allow me to assign the following users: iamneha.

    Note that only kubernetes-client members and repo collaborators can be assigned.
    For more information please see the contributor guide

    Details

    In response to this:

    /assign @iamneha

    Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

  10. fejta-bot commented on Apr 26, 2019

    @fejta-bot

    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

  11. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 26, 2019
  12. fejta-bot commented on May 26, 2019

    @fejta-bot

    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

  13. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 26, 2019
  14. fejta-bot commented on Jun 25, 2019

    @fejta-bot

    Rotten issues close after 30d of inactivity.
    Reopen the issue with /reopen.
    Mark the issue as fresh with /remove-lifecycle rotten.

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

  15. k8s-ci-robot commented on Jun 25, 2019

    @k8s-ci-robot
    Contributor

    @fejta-bot: Closing this issue.

    Details

    In response to this:

    Rotten issues close after 30d of inactivity.
    Reopen the issue with /reopen.
    Mark the issue as fresh with /remove-lifecycle rotten.

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

    Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentation_onlygenerated-client-updatedhelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.help-neededkind/featureCategorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions