reshaprio/reshapr

At some point in the MCP Server tuning/development lifecycle, the user may want to convert the created artifacts into Kubernetes Custom Resource to make their deployment totally reproducible in other steps of the deployment lifecycle using a GitOps approach. This is actually a basic thing, as transforming an artifact into a Custom Resource is just wrapping it with Kubernetes metadata, but we have to think about where to make this option available: Via the CLI? Via the Web UI? Should it be something available via the API but only implemented in the clients (CLI & Web UI)? Should we also plan to build some kind of bundle to wrap many Custom Resources together and create a coherent package? I'd like to hear from the community on the different options and ideas around this.

Web UI was first initialized using the @lucide/svelte icons package and then moved to @hugeicons/svelte because of the many more icons available. However, we still have some Lucide icons in some remaining pages... For better consistency, lighter package weight and less maintenance, it will be great to rationalize and finalize the migration to HugeIcons. Here's a mapping table below: Lucide (@lucide/svelte/icons/…) Hugeicons (@hugeicons/core-free-icons) check Tick02Icon x Cancel01Icon search Search01Icon trash-2 Delete02Icon pencil PencilEdit02Icon minus MinusSignIcon ellipsis-vertical MoreVerticalIcon chevron-right ArrowRight01Icon chevron-down ArrowDown01Icon chevron-up ArrowUp01Icon plus PlusSignIcon copy Copy01Icon key-round Key01Icon user-lock UserLock01Icon message-square-lock MessageLock02Icon

As of today, CLI is targeting only the end-users of Reshapr. Admin operations are only available via shell scripts provided as examples of how to use the APIs or via the We UI. Here's a list of operations and whether they are available via script or UI: Feature Script Web UI  Creating a new user   ✅ ✅  Creating a new organization   ✅ ✅ Assigning quotas to an org   ✅ ⛔ (see #345) Managing memberships   ⛔ ⚠️ (see #346) Creating service account   ✅ ⛔ As using the Web UI is convenient, its deployment is still optional. The first question is whether we should also consider making the above features into CLI commands, or if providing scripts using the raw admin API is enough. If the answer to the above question is "yes", then we must define how the CLI will have access to the admin API that requires admin authentication (using the admin API key that is defined at Reshapr deployment). We can easily provide reshapr admin <command> like commands

From the beginning, we planned to have user/organization membership management, but we didn't define how to use it. The only thing possible at the moment is to assign membership from the Web UI at the time of the user creation. It's not possible after that to come back and change things. We need to add the ability for a user - when she is defined as the owner of an organization - to manage memberships and to allow her to make other users members of this organization. The trick here (as Reshapr is made to be multitenant) is that we shouldn't give the owner the ability to browse the user list and be aware of who is using Reshapr. Membership management should be done only by email address (property typed by the owner), and then the system should say "OK, I added he/her as a member" or "This email address does not match any existing user account". Likewise, the owner should also be able to remove members from an organization.

We should add "Operations" just beside "Included" so that the information will be clearer: