new modues extension and custom_action

[resmo]

No description provided.

[Copilot]

Pull request overview

This PR adds two new Ansible modules to the ngine_io.cloudstack collection—extension and custom_action—to manage CloudStack Extensions and their Custom Actions, along with new integration test targets and action-group registration.

Changes:

• Added plugins/modules/extension.py to manage CloudStack extensions, including registration/unregistration with resources.
• Added plugins/modules/custom_action.py to manage custom actions belonging to an extension.
• Added integration test targets for both modules and registered them in meta/runtime.yml action groups.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
tests/integration/targets/extension/tasks/main.yml	New integration playbook covering extension create/update/details/state/idempotence flows.
tests/integration/targets/extension/meta/main.yml	Adds cs_common dependency for the extension integration target.
tests/integration/targets/extension/aliases	Registers the extension integration target in cloud/cs and cs/group1.
tests/integration/targets/custom_action/tasks/main.yml	New integration playbook covering custom_action lifecycle, parameters/details, and idempotence.
tests/integration/targets/custom_action/meta/main.yml	Adds cs_common dependency for the custom_action integration target.
tests/integration/targets/custom_action/aliases	Registers the custom_action integration target in cloud/cs and cs/group1.
plugins/modules/extension.py	New module implementing CloudStack extension present/absent and register/unregister operations.
plugins/modules/custom_action.py	New module implementing custom action present/absent operations and normalization/diffing.
meta/runtime.yml	Adds custom_action and extension to the CloudStack action group list.

Suppressed comments (1)

plugins/modules/custom_action.py:490

• absent_custom_action() currently fails if the referenced extension does not exist (via get_extension_id()->fail_json), but the integration test expects removing a custom action from an unknown extension to be a no-op (not changed).

    def absent_custom_action(self):
        custom_action = self.get_custom_action()
        if custom_action:

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Suppressed comments (1)

plugins/modules/custom_action.py:291

• get_custom_action() should handle the case where get_extension_id() returns None (e.g., state=absent with a missing extension) and return None instead of calling listCustomActions with an invalid extensionid.

    def get_custom_action(self):
        args = {
            "extensionid": self.get_extension_id(),
            "name": self.module.params.get("name"),
        }
        custom_actions = self.query_api("listCustomActions", **args)
        if custom_actions:
            # The name filter of listCustomActions matches exactly.
            self.custom_action = custom_actions["extensioncustomaction"][0]
        return self.custom_action