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
If I delete a recipe from all stacks, and then click on cookbook attributes, the old attributes for the recipe are still shown in the "cookbook attributes" tab.
The text was updated successfully, but these errors were encountered:
Attributes are cookbook level to Karamel, it doesn't know which recipe uses which attribute. While user have a cookbook reference defined in the cookbooks section of the cluster definition, user can use its attribute in the global level but not in the group level unless at least a recipe from that cookbook is added into group. This is handled in the yaml but not in the designer, we even don't have possibility in the designer to change global settings such as provider and cookbooks.
I think a prerequisite for this task is to have both designer and yaml editor, two viewers of the same model that is working tightly with core. That way we hide very tiny details from the designer and we leverage validations in the core.
If I delete a recipe from all stacks, and then click on cookbook attributes, the old attributes for the recipe are still shown in the "cookbook attributes" tab.
The text was updated successfully, but these errors were encountered: