🌟 Community Feature Challenge: Authorization Modeling 🌟

[gemanor]

Think you can manage authorization modeling better from the CLI? Do you have a new idea for access control modeling? This is one of our 10 community feature challenges, and we want your input on how we can enhance the Permit CLI in the area of Authorization Modeling. This is a space for you to share your ideas on what would make this part of the CLI even better!

How to Participate

• Submit Your Proposal: Comment below with your detailed feature idea. Be sure to explain how it would work and why it would be valuable for users.
• Vote for Your Favorites: Show support for your favorite ideas by upvoting them. Your votes will help us identify the most impactful proposals.
• Win a Bounty: The idea with the most upvotes will be selected, and we’ll put a bounty on it! This means that you (or another contributor) could bring this feature to life and earn a reward.

Why Join In?

• Shape the Future: Your input will directly influence Permit CLI’s growth.
• Community Recognition: Contributing ideas or supporting others’ ideas lets you stand out as a valuable community member.
• Collaborative Ownership: Together, we’ll build a CLI that truly reflects the community’s needs and creativity.

What’s Next?

We’ll keep this challenge open for proposals and upvotes until November 10th, 2024. Once the top idea is chosen, we’ll update this issue with details on the bounty and next steps for development.

Thank you for helping us make the Permit CLI even better. We can’t wait to see what you come up with! 🌟

[quest-bot]

New Quest!

A new Quest has been launched in @permitio’s repo.
Merge a PR that solves this issue to loot the Quest and earn your reward.

---

Loot of 250 USD has been stashed in this issue to reward the solver!

🗡 Comment @quest-bot embark to check-in for this Quest and start solving the issue. Other solvers will be notified!

⚔️ When you submit a PR, comment @quest-bot loot #7 to link your PR to this Quest.

Questions? Check out the docs.

[naaa760]

@quest-bot embark

[quest-bot]

@naaa760 has embarked on their Quest. 🗡

• @naaa760 has been on GitHub since 2024.
• They have merged 3 public PRs in that time.
• Their swords are blessed with Shell and JavaScript magic ✨
• They haven't contributed to this repo before.

This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.

Questions? Check out the docs.

[naaa760]

Hello @gemanor :)
I would like to work on this issue, please assign me Thank You

[Shr11]

@quest-bot embark

[quest-bot]

@Shr11 has embarked on their Quest. 🗡

• @Shr11 has been on GitHub since 2022.
• They have merged 9 public PRs in that time.
• Their swords are blessed with Python and Jupyter Notebook magic ✨
• They haven't contributed to this repo before.

This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.

Questions? Check out the docs.

[ChiragAgg5k]

@quest-bot embark

I would like to propose Access Control Policy Language (ACPL) integration.

How this would work is:

1. Policy Syntax: users can define policies using very human readable syntax. For eg.

   • role "admin" can "view" on "users" resource
   • role "editor" can "edit" on "articles" where "author" is "self"

2. Modular Policies: Import policies from reusable modules. For eg. the read_only module can be defined in one place and imported whereever necessary.

3. Policies using CLI: Ability to create and manage policies using the CLI itself. Eg. permit policy create

4. Conditional Access: Ability to create policies that take in conditions for access eg. only during office hours

These were some of the improvements I had in mind. Do let me know if they were helpful. Thanks

[quest-bot]

@ChiragAgg5k has embarked on their Quest. 🗡

• @ChiragAgg5k has been on GitHub since 2022.
• They have merged 125 public PRs in that time.
• Their swords are blessed with Shell and CSS magic ✨
• They haven't contributed to this repo before.

This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.

Questions? Check out the docs.