Fix parameter name in ConfigMapLock.create docstring

[LALITH0110]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

ConfigMapLock.create documented :param electionRecord:, but the parameter is named election_record:

def create(self, name, namespace, election_record):
    """
    :param electionRecord: Annotation string

So the docstring described a parameter that does not exist on the method, while the real one was left undocumented. This corrects the name to match the signature.

The change is in kubernetes/base/leaderelection/resourcelock/configmaplock.py. Note kubernetes/leaderelection is a symlink into kubernetes/base/, so there is a single real file and no second copy to update.

One line. Documentation only — no behaviour change.

Which issue(s) this PR fixes:

None — found by comparing documented :param entries against actual function signatures.

Special notes for your reviewer:

The documented parameters on create now exactly match its signature (name, namespace, election_record). Nothing under kubernetes/client/ was touched, so no generated code is affected, and no tests reference leaderelection.

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: LALITH0110 / name: LALITH0110 (99a1e3c)

[kubernetes-prow]

Welcome @LALITH0110!

It looks like this is your first PR to kubernetes-client/python 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/python has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[yliaog]

thanks for the PR
/lgtm
/approve

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LALITH0110, yliaog

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• kubernetes/base/OWNERS [yliaog]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment