# Newbie, what's a good plugin development workflow?

**URL:** <https://forum.ansible.com/t/newbie-whats-a-good-plugin-development-workflow/38133>\
**Category:** Ansible Developer\
**Tags:** galaxy-ng\
**Created:** [June 20, 2023, 8:52pm UTC](https://forum.ansible.com/t/newbie-whats-a-good-plugin-development-workflow/38133 "2023-06-20T20:52:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kent\_Larsson](https://avatars.discourse-cdn.com/v4/letter/k/fbc32d/32.png) [@Kent\_Larsson](https://forum.ansible.com/u/Kent_Larsson)\
**Post date:** [June 20, 2023, 8:52pm UTC](https://forum.ansible.com/t/newbie-whats-a-good-plugin-development-workflow/38133/1 "2023-06-20T20:52:47Z")

</div>

Hi,

I’m about to create a vars\_plugins to read a JSON, modify it quite heavily and then expose it as a variable for my playbooks.

What is a good development workflow? Do I have to run the plugin as part of a playbook repeatedly? How do you work when creating a plugin?

And if it turns out usable, what is the best way to publish it at Ansible Galaxy in the (probably far) future? A collection feels a bit much as it’s only one plugin, but perhaps it’s best practise?

Have a great day!