1. This is for simplicity as file name doesn't really matter. HOT
processing code needs to know where to look for template and it is easier
to have fixed file name/location rather than force users to explicitly
specify location in package manifest. But if if you have valid case where
this becomes
These two subjects have probably been discussed already, but I couldn't find
any info on them, so very much appreciate if someone could clarify.
1. Why is the HOT template that is fed to package-create command renamed to
template.yaml? Any issue with keeping the original name?
2. Why HOT syntax
Hello,
These two subjects have probably been discussed already, but I couldn't
find any info on them, so very much appreciate if someone could clarify.
Why is the HOT template that is fed to package-create command renamed to
template.yaml? Any issue with keeping the original name?
Why HOT
