Hello Foreman users, I wonder how people using multiple organizations in Foreman manage their puppet modules. Let's assume I have two organizations A and B and I want them to be isolated as much as possible. Since puppet environments can be scoped to organization, we can have separate environments for each organization. Well, as long as they have unique name, since the validation prevents to have two environments with the same name even if they are in different organizations.
But the bigger issue seems to be is how puppet classes should work, since they are not scoped to organizations. When user in organization B tries to import the class with the same name that users from organization A already imported, it fails saying the name has already been taken. In theory the organization should be clear from environment but what if I have two separate environments for organizations and they want to use same puppet module? And what if their puppet modules have different versions so the smart class parameters differs? And does using katello content views with puppet modules helps in this case? It creates different puppet environment for each content view version but is there the same problem for puppet class name collision? Is there some workflow I'm missing? If you have such use case but yout (same as me) can't solve it with Foreman, how would you change Foreman so it fulfills your needs? Thanks for any suggestions -- Marek -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
