Repository navigation
Add per-store manifests, multi-store provisioning, and dashboard - #8
Merged
Merged
Conversation
store-manifests renders everything one store needs in its own namespace: quota and limit range, default-deny policies that admit only the gateway to the store's MCP server, MariaDB, WordPress with its Ingress, the bootstrap Job named by its spec, and the Woo MCP server. One function derives every host, URL and MCP origin from the slug. StoreCluster applies objects with server-side apply and refuses any namespace outside storelink-store-*, and deletes only namespaces labelled as managed. The upstream policy can approve exactly the provisioned store MCP origin form. The ServiceAccount HTTPS code is shared with the credential store.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces multi-store provisioning to the StoreLink platform, enabling users and teams to create, manage, and delete multiple independent WooCommerce stores directly from the dashboard. The changes span the frontend, documentation, CI/CD, and Kubernetes Helm charts, ensuring the feature is robust, secure, and well-documented.
Multi-store provisioning and dashboard integration:
Added a new
Storestab to the dashboard, allowing users to create, retry, and delete stores, view per-user and per-team limits, and monitor store status with real-time updates. Includes UI for store creation, deletion confirmation, and error handling. (apps/dashboard/src/main.tsx,apps/dashboard/src/stores.tsx,apps/dashboard/src/style.css) [1] [2] [3] [4] [5] [6] [7]Updated the dashboard and documentation to reflect the new multi-store capabilities, including navigation, feature lists, usage guides, and verification steps. (
README.md) [1] [2] [3] [4] [5]Kubernetes and Helm chart enhancements:
charts/storelink/templates/apps.yaml,charts/storelink/templates/network-policies.yaml) [1] [2] [3]Testing and CI/CD improvements:
.github/workflows/ci.yaml)