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
@mayn wow, thank you for the amazing turn around! I had poked around the code and didn't see anything obvious jump out at me...never would have thought that the troposphere code would cause a conflict.
@elasticdog yeah no problem.
It looks like the name conflict is because of the similarities between packer and python PEP8 naming convention (use of snake_case).
troposphere project is not affected because AWS cloudformation uses a naming convention closer to PascalCase while troposphere is snake_case.
So the props definitions would never overlap the python code that is used to dynamically generate itself (they would just be set on the object as attributes using PascalCase)
packerlicious version
1.4.0 -> 1.4.1
Expected behavior
The provided
attributes
property should end up in the final provisioner configuration:Actual behavior
The provided
attributes
property is silently discarded in the final provisioner configuration:Steps to reproduce
See above...
The text was updated successfully, but these errors were encountered: