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

Basic user mgmt #47

Merged
merged 64 commits into from
Aug 16, 2019
Merged

Basic user mgmt #47

merged 64 commits into from
Aug 16, 2019

Conversation

tobiaslohr
Copy link
Contributor

@tobiaslohr tobiaslohr commented Jul 15, 2019

  • Exploring Account Manager orgs and users
  • Management of Account Manager users incl. CRUD operations and grant/revoke of roles to/from users in Account Manager
  • Management of Business Manager users incl. querying users, CRUD operations and grant/revoke of roles to/from users in Business Manager

…ogin <login> to read details of a single users
Copy link
Collaborator

@hnestmann hnestmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have mostly checked the CLI and scrolled over the rest. Seems good. I just think we should get consistent with stuff:get

README.md will miss a few explanations. We can deliver later - if we file a ticket for it. Same for unit tests

console.log(' Examples:');
console.log();
console.log(' $ sfcc-ci org:list')
console.log(' $ sfcc-ci org:list --org "my-org"')
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't this be org:get?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was following an approach to read list(s) of objects, which optionally can be narrowed down to a single unique object, like

  • org:list, org:list --org <org>
  • user:list, user:list --login <login>
  • roles:list, role:list --role <role>

The only exception still is sandbox:list and sandbox:get, which I plan to merge into a sandbox:list --sandbox <sandbox>

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK - I like the pattern, I was commenting for consistency.

I thought there are more getters, but since I work a lot with sandbox:get I was wrong.

So in summary we need three tickets

  • Unit Tests Completion
  • Documentation
  • Refactor sandbox:get

cli.js Show resolved Hide resolved
console.log();
console.log(' $ sfcc-ci role:grant --login the-user --role the-role');
console.log(' $ sfcc-ci role:grant --login the-user --role the-role --scope zzzz_dev');
console.log(' $ sfcc-ci role:grant --login the-user --role the-role --scope zzzz_*');
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lovely

cli.js Show resolved Hide resolved
lib/org.js Outdated Show resolved Hide resolved
lib/org.js Outdated Show resolved Hide resolved
lib/role.js Outdated Show resolved Hide resolved
@tobiaslohr tobiaslohr requested a review from SGD1953 July 17, 2019 08:10
@tobiaslohr
Copy link
Contributor Author

@kdomachowski @SGD1953 @hnestmann can you re-review based on the latest changes please? thanks

@tobiaslohr tobiaslohr merged commit f58c1fa into master Aug 16, 2019
challmannsf pushed a commit that referenced this pull request Oct 29, 2019
@tobiaslohr tobiaslohr added this to the 2.1.x milestone Nov 12, 2019
@tobiaslohr tobiaslohr deleted the basic-user-mgmt branch February 19, 2020 08:12
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

Successfully merging this pull request may close these issues.

4 participants