-
Notifications
You must be signed in to change notification settings - Fork 8
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
Component Discovery With Reclass #160
Conversation
As from today's sync: Tested to access a puppet profile variable in hiera, it doesn't seem to be working. |
Please also make sure that this is documented, maybe needs to be done after #147 has been merged. |
As discussed during the SYNc today: Since this is also not allowed in Puppet and it's probably better that way anyway, we'll proceed with this approach and from now on don't allow parameters which are set in components to be referenced from the inventory. |
Currently testing this for some "common" usecases. What I found so far is that with this approach we'll have to rethink how local mode works, as you now can't just add a component in the inventory somewhere and run |
I don't think I understand the problem. This wasn't possible before either? |
It is currently possible for any component that the file-based discovery mechanism finds and downloads. |
To be able to use the exposed option of ignoring missing classes in Kapitan.
So the inventory is ready and all files and directories are where they should be.
By enabling `ignore_class_notfound` missing component classes are ignored.
One consequence of this is, that the hierarchy can't reference parameters which are defined in component classes (i.e. defaults). This is due to the fact that a reclass inventory must be able to resolve all references in order to be rendered. There's no mechanism to ignore invalid references (like there is for ignoring inexistent class files).
Checklist
Closes #138