No ability to use custom salt jinja2 filter in custom cloud deploy scripts #52442
Labels
Confirmed
Salt engineer has confirmed bug/feature - often including a MCVE
Feature
new functionality including changes to functionality and code refactors, etc.
Salt-Cloud
Milestone
Description of Issue/Question
When writing deploy scripts
vm
,opt
, andminion
dicts are available.minion is
str
, butvm
andopt
are dicts, and we can't dump them directly.The problem is that if you need to dump/pass information that is json/yaml, you don't have the ability to do that from the deployer script, because no json/yaml filter is available.
I'm not sure if it is intended or not, but would be nice to have an ability to use them.
Setup
I have a custom cloud deployer with "custom" opts:
Then in my custom deployer script I have (just an example)
Steps to Reproduce Issue
If you deploy a VM with the custom deployer script you will see an error and traceback:
and the raw dump of data looks like:
Versions Report
The text was updated successfully, but these errors were encountered: