Re: [tosca] terminology for naming TOSCA files and templates

On Mon, Jun 28, 2021 at 6:21 PM Chris Lauwers <lauwers@ubicity.com> wrote:

That could work, but there are TOSCA files that are neither service templates nor profiles (e.g. the files that are imported by service template files).

Well, we still need to better define what a profile is. I understand it as any collection of files that doesn't have the template assignments. The profile can be one file or can import many others. I tend to divide my profiles into many files.

Where such a collection becomes more than just "a bunch of types" and an actual real "profile" may be due to simply giving it that profile/namespace thing we discussed in the past.

Also, if we did away with the topology_template keyword, then it would be slightly harder to validate âuniquenessâ of the keys. For example, can I have a top-level template that defines node_templates, and then import a separate TOSCA file that defines policies?

Only slightly harder. We could clearly list the specific keywords that are only allowed in service templates. (Again, this is what Cloudify has been doing for years.) To be honest, I kinda wish all of the keywords had the "_template" suffix, like node_templates. So it would be policy_templates, group_templates, etc.

The big win is removing a keyword that does ... nothing at all (except make service templates have too much indentation).

tosca message