Accesspoint location workflow manager

[md-rafeek]

Type of Change

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

Description

New Module - Access point Location workflow manager
This module sub set of Site workflow module, need to create the planned location in the floor, and assign the Access point to the Planned floor location.
As a part of this module we have covered below scenario

1. Create the Access point planned location
2. Idempotent for the create planned location.
3. Update the access point planned location.
4. Delete the Access point planned location
5. Idempotent for the Delete planned location
6. Create Planned location and assign the Access point to the Planned location in single config
7. Assign the Access point with already planned location
8. Un assign or Remove from floor location

Enhancement:
This module sub set of Site workflow module, need to create the planned location in the floor, and assign the Access point to the Planned floor location.
Enhancement Description: [Explain what was enhanced, why, and how]
Impact Area:
New Module Hence not impact with any other module.

Pending on UT/IT

Testing Done:

• Manual testing
• Unit tests
• Integration tests

Test cases covered: [Mention test case IDs or brief points]

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