New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow (JSON formatted) input strings to be dictionaries #1883
Comments
I really though this would simplify my current sources, so I implemented it :-) Please have a look at give me some feedback.
|
Hi @tma-unwire - as you noted in your AWS Native issue, this is behavior that could be great to implement elsewhere as well. I would be curious to see if you had interest to bring this to pulumi/pulumi SDK generation implementation so it is available across all providers, provided the maintaining team is open to the idea. cc @stack72 for thoughts on this? |
I'll be happy to do that. It misses some tests, but otherwise it works fine for me as is. So you're welcome to take the code, modify, include, delete, etc as you see fit... The 'json.dump(...)' could be supplied as an argument and that way we could support YAML and other sorts of serializations. |
@tma-unwire - we would love to see a PR with your suggested changes if you're up for it! :) |
I found an error. New version below:
|
This feature has been implemented in pulumi/pulumi#11607. |
Hello!
Issue details
When working with AWS resources you often have input parameters that are JSON formatted strings that contains the configuration for the resource. A typical example is the various IAM resources with roles and policies. Sometimes these even include Output from other resources.
In all cases, it can be nice - and a lot more readable - to inline the dictionary instead of having to use json.dumps(...), Output.apply(...) or even Output.all(...).apply(...)
A real world example
It would be so much nicer to be able to write this:
As value is defined as a string, then Pulumi should automatically wait ion the result and jsonify the results..
Affected area/feature
Primarily in AWS, but something similar could also be useful in Kubernetes.
The text was updated successfully, but these errors were encountered: