Bug #1697
The puppet modules are shown in all environments, while should be limited to the environment they reside in.
| Status: | Closed | Start: | 06/21/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | % Done: | 100% |
||
| Category: | Web Interface | |||
| Target version: | 1.0 | |||
| Backlog: | No | Difficulity: | ||
| Votes: | 0 |
Description
The puppet modules are shown in all environments, while should be limited to the environment they reside in.
The situation is as following:
Someone create a puppet module under a particular environment on the file system (under /etc/puppet/modules/<environment name>/). When I add this module to foreman, I see it under all environments and I'm able to add it to any hostgroup that resides in any environment.
I'd expect having the modules added under a particular environment to be available only for that environment. Seeing modules from other environments is very confusing and forces checking the existence of the files on the host.
Thanks.
Associated revisions
Revision 8f34dc60a421cc7c9cd146db7bc5031a0b18fed8
fixes #1697 - hostgroup class listing showed all classes regardless of environment
History
Updated by Ohad Levy 11 months ago
- Category set to Web Interface
- Assigned to set to Ohad Levy
- Target version set to 1.0
Updated by Ohad Levy 11 months ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset 8f34dc60a421cc7c9cd146db7bc5031a0b18fed8.
