Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Not respecting declaration of user-of-record userid via base config example #54

Open
GitBytes opened this issue Jun 21, 2019 · 1 comment

Comments

@GitBytes
Copy link

Pacifica CLI Tool version

v0.4.0

Platform Details

RHEL 6.6, Python3.6 (Conda)

Scenario:

Trying to use the base uploader.json metadata profile config to define cli option for user of record.

Steps to Reproduce:

set --user-of-record and verify the chosen userid has been passed through to the final transaction metadata details upon successful upload.

Expected Result:

user-of-record to be id 12345 when declared via cli

Actual Result:

Some other user id appears in the user-of-record id field (maybe PI?, not really sure the condition for end result).

@dmlb2000
Copy link
Member

@GitBytes I'm not able to reproduce this issue. After I've added the user ID, project ID and relationship UUID to the project_user table the user appeared in the list of available users. I tested this in both interactive and non-interactive ways.

The thought to check the metadata before uploading is try doing a --dry-run and --interactive to validate the user you are looking for shows up in the list returned from the user of record query.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants