Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TOSCA types for specific locations should be imported in a4c when importing the plugin itself #28

Open
loicalbertin opened this issue May 28, 2021 · 1 comment

Comments

@loicalbertin
Copy link
Member

loicalbertin commented May 28, 2021

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.

@loicalbertin
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant