You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bases on an IRC discussion we had on #ansible-devel it was suggested to rename the module to make it easy for users to use it, especially as we aim to make it an ansible core module.
Proposals so far:
yaml
yaml_file - similar to ini_file, only downside is that it will be an issue if we ever want to add support for "content" as alternative to "src" as calling parameter.
Someone noted that JSON support could be wanted in the future and that the module could do both. Still, I think that this is outside the current scope and even if we endup implementing that we could create a module alias that does that for json, so we can reuse the codebase.
Please comment with your suggestions/votes.
The text was updated successfully, but these errors were encountered:
Bases on an IRC discussion we had on #ansible-devel it was suggested to rename the module to make it easy for users to use it, especially as we aim to make it an ansible core module.
Proposals so far:
yaml
yaml_file
- similar toini_file
, only downside is that it will be an issue if we ever want to add support for "content" as alternative to "src" as calling parameter.Someone noted that JSON support could be wanted in the future and that the module could do both. Still, I think that this is outside the current scope and even if we endup implementing that we could create a module alias that does that for json, so we can reuse the codebase.
Please comment with your suggestions/votes.
The text was updated successfully, but these errors were encountered: