Description of problem:
Lets say there are two proxies, external A and internal B.
If Puppet environment wasn't synced to one of capsules, then import from that capsule will suggest to remove\add the classes\environment.
This requires the user to hand pick the correct changes.

How reproducible:
Always

Steps to Reproduce:
1. Add two capsules to the organization with life cycle Library
2. Publish new Content view with Puppet modules to life cycle Library
3. Make sure the Environment doesn't exist on one of the capsules (This can happen for many reasons) for example Capsule A.
4. Go to Puppet environments page
5. click "import from capsule-a.com" at the top of the page

Actual results:
In the list of changes, there will be an option to remove the puppet environment we created. This is undesired.

Expected results:
List of changes that are correspond to description in Foreman.

Additional info:
This happens regardless of whether synced content is used. It can simply be reproduced by having 2 Puppet proxies. When both proxies have an environment with the same name but different modules and we try to import from both, we end up changing the same environment in Foreman. Keeping reference to the proxy we used for import of particular environment would solve the problem. It would also improve multitenancy as each organization could use its own proxy for imports without clashes on environments.