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

Cookbook attributes still shown for a recipe even after it has been deleted from all stacks #12

Closed
jimdowling opened this issue Mar 24, 2015 · 1 comment

Comments

@jimdowling
Copy link
Contributor

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.

@kamalhakim
Copy link
Member

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.

kouzant added a commit to kouzant/karamel that referenced this issue Sep 7, 2023
SirOibaf pushed a commit to SirOibaf/karamel that referenced this issue Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants