This repository has been archived by the owner on Feb 1, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Introduce more separation to graphs #50
Labels
enhancement
New feature or request
Comments
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 14, 2020
…d namespaces and updating tests.
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 14, 2020
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 21, 2020
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 21, 2020
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 24, 2020
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 24, 2020
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 24, 2020
Conflicts: infrastructure/lib/rest-api/lambdas/add_graph_request.py infrastructure/lib/rest-api/lambdas/delete_graph_request.py infrastructure/lib/rest-api/lambdas/get_graph_request.py infrastructure/lib/rest-api/lambdas/graph/__init__.py infrastructure/test/database/graph-database.test.ts infrastructure/test/e2e/client/rest-api-client.ts infrastructure/test/e2e/integration.test.ts infrastructure/test/e2e/setup/cluster-helper.ts
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 25, 2020
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 25, 2020
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 25, 2020
m29827
added a commit
to m29827/Kai
that referenced
this issue
Sep 28, 2020
m29827
added a commit
to m29827/Kai
that referenced
this issue
Nov 4, 2020
Conflicts: infrastructure/lib/rest-api/lambdas/graph/__init__.py infrastructure/lib/workers/lambdas/add_graph.py infrastructure/lib/workers/lambdas/kubernetes/__init__.py infrastructure/test/e2e/integration.test.ts
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
All graphs currently have to have unique names as they all share the default namespace. If users could create and use different namespaces, they could re-use graph names and from an admin point of view, it will be easier to locate problems with a graph if they are searching through a namespace with 5 graph deployments in rather than 50.
It would also allow users to make use of test / dev / ref namespaces to use as a sort of environment and allow teams to keep their graphs within their own namespace.
The text was updated successfully, but these errors were encountered: