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
Currently TOSCA types specific to a given location (GCP, AWS, Slurm, and so on...) are imported in Alien when creating the first location of this given type.
This is particularly painful when importing TOSCA components that reference those location-specific types as we should first create a location. Importing a whole git forge can be a nightmare in this case.
I do not see any reason to not import these types when we import the plugin as we do for Yorc global/generic types.
The text was updated successfully, but these errors were encountered:
Ok finally found why we do it this way:
When importing TOSCA types globally at the plugin level the logic in Alien is first to parse all types then index them into the catalog. So if we do have imports that reference types that are also at plugin level then Alien fails to parse them.
Currently TOSCA types specific to a given location (GCP, AWS, Slurm, and so on...) are imported in Alien when creating the first location of this given type.
This is particularly painful when importing TOSCA components that reference those location-specific types as we should first create a location. Importing a whole git forge can be a nightmare in this case.
I do not see any reason to not import these types when we import the plugin as we do for Yorc global/generic types.
The text was updated successfully, but these errors were encountered: