# How to register secrets - as plugin developers, and users?

**URL:** <https://forum.ansible.com/t/how-to-register-secrets-as-plugin-developers-and-users/46448>\
**Category:** Project Discussions\
**Tags:** security, ansible-devel\
**Created:** [October 11, 2026, 9:03pm UTC](https://forum.ansible.com/t/how-to-register-secrets-as-plugin-developers-and-users/46448 "2026-10-11T21:03:31Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [October 12, 2026, 9:23pm UTC](https://forum.ansible.com/t/how-to-register-secrets-as-plugin-developers-and-users/46448/3 "2026-10-12T21:23:48Z")

</div>

> [@jborean](#):
>
> I’m sorry I don’t have a good suggestion here, I’m just not sure how this can be done generically without overcomplicating the implementation or UX of such a plugin.

I don’t think there is a generic way to handle this for _all_ cases, but I think that a (small) set of more generic filters could cover most cases.

A filter which accepts input (that it returns unchanged, unless some `eat=true` parameter is passed) and a sequence of inclusion/exclusion [JSON query paths](https://jmespath.org/examples.html) (as used by community.general.json\_query) / [jq expressions](https://jqlang.org/manual/#basic-filters) ([used in other contexts](https://forum.ansible.com/t/45595)) / something similar to select secret values (or reject non-secret values), would likely already cover a lot of cases.

Being able to define schemas for this (maybe stored as ansible vars, or also in other ways?) and reusing them in multiple places would likely also be useful, if you need to process similar lookup/query results in different places.

---

_[View the full topic](https://forum.ansible.com/t/how-to-register-secrets-as-plugin-developers-and-users/46448)._