You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Let's say a user directory of for example TESTDIR is defined in the config file, and a owner of the newly created app of USER1 is specified.
If user TESTDIR/USER1 does not have permissions to access the template apps, the app duplicator will not be able to verify that the specified app really is tagged as a template app, with a failed app creation as a result.
This is how the app duplicator was designed, but the drawback is that all users using the tool must also be given access to the template apps. This will result in those template apps showing up in the Hub, potentially confusing users.
Expected behavior
This is a really a design change:
Use internal user accounts when interacting with the QRS APIs.
As a final step change owner of the created app, to the user specified in the call to the app duplicator's API.
The text was updated successfully, but these errors were encountered:
Describe the bug
Let's say a user directory of for example TESTDIR is defined in the config file, and a owner of the newly created app of USER1 is specified.
If user TESTDIR/USER1 does not have permissions to access the template apps, the app duplicator will not be able to verify that the specified app really is tagged as a template app, with a failed app creation as a result.
This is how the app duplicator was designed, but the drawback is that all users using the tool must also be given access to the template apps. This will result in those template apps showing up in the Hub, potentially confusing users.
Expected behavior
This is a really a design change:
The text was updated successfully, but these errors were encountered: