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.

Sign up for GitHub

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

Jump to bottom

Spike: Define permissions #51

Closed
pamlo412 opened this issue Sep 21, 2020 · 3 comments
Closed

Spike: Define permissions #51

pamlo412 opened this issue Sep 21, 2020 · 3 comments
Labels
In epic 2 Issue is a child in the indicated parent epic spike V1.0 MVP Indicates the release version for the issue

Comments

@pamlo412
Copy link
Contributor

pamlo412 commented Sep 21, 2020 •
edited
Loading

This spike is to define the specific permissions we will allow admin users to set for end users of the Smart Hub.

Goals of this spike:

Dev notes:
Starting place for discussion is these possible permission categories:

  • ADMIN - Can edit users with the admin UI
  • APPROVE_REPORTS
  • READ_REPORTS - Can view activity reports for the region
  • READ_WRITE_REPORTS - Can view and update/create activity reports for the region
This was referenced Sep 21, 2020
Open
Open
Closed
@pamlo412 pamlo412 added the spike label Sep 21, 2020
@pamlo412 pamlo412 mentioned this issue Sep 22, 2020
Closed
@rahearn
Copy link
Contributor

rahearn commented Sep 23, 2020

Is this a spike, or just a placeholder for a meeting between some of us to review the results of #39 and agree on the first set of permissions to implement as part of #52? I want us to be mindful that we won't have the full set of permissions needed for the system, or even the MVP, and that's ok.

@pamlo412
Copy link
Contributor Author

@rahearn - this issue is a spike representing a dependency: we want the initial permissions to be agreed upon before we begin work on #50. It probably would be best handled via a meeting. To my thinking, that doesn't mean it's not a spike.

I'm surprised to hear you say we can't decide yet on the full set of permissions for the MVP. I definitely want to be part of the meeting in which we figure out what's possible, so I understand any constraints necessitating more permissions work, beyond this setup story, for the MVP.

@pamlo412
Copy link
Contributor Author

Discussed this issue at standup today and agreed that we can start with the above list of permissions. I updated #50 and am closing this spike.

rahearn pushed a commit that referenced this issue Oct 26, 2020
@SarahJaine
Terraform Init (#51)
5648369 
* add notes

* second round of notes

* move state management infra to seperate main

* add tf readme, remove aws

* bootstrap/variables.tf

* refine bootstrap, test fmt

* test hook

* rename hook

* update variables, finish tf readme

* update description of infrastructure types, change headers

* remove backend, assume s3 bucket exists

* use service-account bucket, update directions to generate

* update README

* add bold

* minor formatting

* update space and org

* add prod, staging

* update to shared-psql

* move aws creds

* give aws cli directions

* change rds plans

* update directions

Co-authored-by: Sarah-Jaine Szekeresh <[email protected]>
rahearn added a commit that referenced this issue Oct 26, 2020
@rahearn
Merge pull request #113 from adhocteam/main
4a5eab5 
Terraform Init (#51)
@pamlo412 pamlo412 added In epic 2 Issue is a child in the indicated parent epic V1.0 MVP Indicates the release version for the issue labels Oct 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
In epic 2 Issue is a child in the indicated parent epic spike V1.0 MVP Indicates the release version for the issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rahearn @pamlo412