Updating demo_scopes.json

[Thingus]

Closes #5735

I have:

• Formatted any Python files with black
• Brought the branch up to date with master
• Added any relevant Github labels
• Added tests for any new additions
• Added or updated any relevant documentation
• Added an Architectural Decision Record (ADR), if appropriate
• Added an MPLv2 License Header if appropriate
• Updated the Changelog

Description

Updates Flowauth quickstart to work with worked examples

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1203640272340521

[cypress]

---

Test summary

4 • 0 • 0 • 0 • 0

---

Run details

Project	FlowAuth
Status	Passed
Commit	1b57efa
Started	Jan 5, 2023 9:21 AM
Ended	Jan 5, 2023 9:22 AM
Duration	00:49 💡
OS	Linux Debian -
Browser	Electron 106

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[codecov]

Codecov Report

Merging #5737 (1b57efa) into master (d095001) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #5737      +/-   ##
==========================================
- Coverage   93.24%   93.24%   -0.01%     
==========================================
  Files         277      277              
  Lines       10828    10829       +1     
  Branches      895      895              
==========================================
  Hits        10097    10097              
  Misses        602      602              
- Partials      129      130       +1     

Impacted Files	Coverage Δ
flowauth/backend/flowauth/models.py	89.31% <100.00%> (+0.04%)	⬆️
flowmachine/flowmachine/core/cache.py	92.30% <0.00%> (-0.39%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[Thingus]

I think that just adding the admin3 scopes to the default role should be enough to make all the worked examples workable - @jc-harrison can you confirm?

[jc-harrison]

I think that just adding the admin3 scopes to the default role should be enough to make all the worked examples workable - @jc-harrison can you confirm?

I think admin3 is all that's needed for the worked examples, but I think I'd argue for enabling all queries in the demo roles - the main purpose of the quick-start is to enable people to try running FlowKit queries, so I think it's good if users can modify the queries as they like and still be able to run them without needing to understand how to enter FlowAuth admin mode and enable more scopes.

[jc-harrison]

Linking this issue here for visibility - at some point it would be good to modify the quick-start so that FlowAuth demo data is populated from the quick-started FlowAPI spec, rather than from a hard-coded pre-defined spec.

[Thingus]

I think admin3 is all that's needed for the worked examples, but I think I'd argue for enabling all queries in the demo roles - the main purpose of the quick-start is to enable people to try running FlowKit queries, so I think it's good if users can modify the queries as they like and still be able to run them without needing to understand how to enter FlowAuth admin mode and enable more scopes.

I'm inclined to agree there - I think that when an org gets into the situation that they'll be needing the finer-grained auth tools, they're probably past the quickstart. Will update.

[jc-harrison]

Looks good. I've tried running through the worked examples in a quick-start deployment, and it's all working fine.