Explore action extensibility/pluggability/packageability

[cidrblock]

trafficstars

Summary

thinking about breaking the action directory into 2:

internal_actions ansible_actions

Each would still behave as a python package, but would position navigator for

controller_actions later

These small steps would position navigator to pull actions from external packages in the future.

At some point in time, the ansible_actions and related runner code, could move do a separate python package, as well as the controller_actions to it's own.

This would allow for innovation at the action level without growth of the navigator code base.

(actions_from would need to be user facing, so actions from any python package could be loaded

• the UI/action API would need to be well defined, as it would be a contract with action authors and need to be versioned

Issue Type

Feature Idea

Additional Information

see above

Code of Conduct

• [X] I agree to follow the Ansible Code of Conduct

[ganeshrn]

Example navigator action https://github.com/ansible/ansible-navigator/issues/577 internal_actions can be named as navigator_actions