Set proper taxonomy scope when importing puppet classes
|Assigned To:||Ondřej Pražák|
|Category:||Organizations and Locations|
|Found in release:||Pull request:||https://github.com/theforeman/foreman/pull/4699|
|Velocity based estimate||-|
User should import puppet classes only to environments that are in his organizations. The previous attempts to fix this do not cover all the cases. Environments have unique name and some workflows trigger the 'Name already taken' validation error.
Steps to reproduce:
1) create 2 organizations, A and B
2) create a_user, give him Manager role and assign him only to A org
3) import some_puppet_env with a couple of classes only into org B
4) switch to a_user, try to import all environments from the same proxy as in previous step
5) observe the error
When importing environments in step 4, some_puppet_env is marked for creation because it was not found in org A, but it already exists in B.