Yaml document related changes code is working fine

[md-rafeek]

Description

[CSCwm83940] - Updating Power Level via Ansible is unsuccessful
[CSCwm47563] - Update documentation to change secondary, tertiary controller names as mandatory field

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• All the sanity checks have been completed and the sanity test cases have been executed

Ansible Best Practices

• Tasks are idempotent (can be run multiple times without changing state)
• Variables and secrets are handled securely (e.g., using ansible-vault or environment variables)
• Playbooks are modular and reusable
• Handlers are used for actions that need to run on change

Documentation

• All options and parameters are documented clearly.
• Examples are provided and tested.
• Notes and limitations are clearly stated.

Screenshots (if applicable)

Notes to Reviewers

[madhansansel]

Do we need to change here or in the code?

[md-rafeek]

In the code i have used powerlevel, hence the api response of AP config also same. i have fixed the code long back forget to change in this document.

[madhansansel]

If power_level is released to customer, then we can use power_level itself.
power_level is more consistent with YAML's preference for clarity and common conventions.

Why did you change power_level into powerlevel in the code?

[md-rafeek]

When we merged first time we used the power_level QA bug was raised not working in power level. then we checked the code. while checking we found update ap config the payload was changed to powerLevel. actually in the payload as well as ap config response, both powerlevel only using. we are using function to convert snake case to camel case to create payload. there we are getting problem. those we fixed in the last bug with powerlevel. that i need to update in the yml document i missed it

[md-rafeek]

addressed the commnets.

[md-rafeek]

In the code i have used powerlevel, hence the api response of AP config also same. i have fixed the code long back forget to change in this document.

[md-rafeek]

if we change to power_level, the dynamic function used for snake_case to camel case will have problem. so we used powerlevel

[md-rafeek]

When we merged first time we used the power_level QA bug was raised not working in power level. then we checked the code. while checking we found update ap config the payload was changed to powerLevel. actually in the payload as well as ap config response, both powerlevel only using. we are using function to convert snake case to camel case to create payload. there we are getting problem. those we fixed in the last bug with powerlevel. that i need to update in the yml document i missed it