-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Namespace.ValidateNamespace to add workspace to arguments #7154
Conversation
Signed-off-by: Josh <josh@liveoak.ws>
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Thanks for your contribution @jhandel! You should run |
…e new mock. Signed-off-by: Josh <josh@liveoak.ws>
sorry about that.. I thought I read somewhere that the generated code wasn't checked in so it could always be re-generated so I kind of ignored that assuming the build would run the generator.. Anyways, generated the updated code and checked.. |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Thanks for your contribution @jhandel ! |
…ius-project#7154) Signed-off-by: Josh <josh@liveoak.ws> # Description in order for the non current context to be used by ValidateNamespaces so that it can create namespaces in the workspaces kubernetes context we need to pass in the workspace and then use workspace.KuberneteContext() to look up the correct context. ## Type of change This pull request fixes a bug in Radius and has an approved issue (issue link required). Fixes: radius-project#5698 --------- Signed-off-by: Josh <josh@liveoak.ws> Signed-off-by: willdavsmith <willdavsmith@gmail.com>
…ius-project#7154) Signed-off-by: Josh <josh@liveoak.ws> # Description in order for the non current context to be used by ValidateNamespaces so that it can create namespaces in the workspaces kubernetes context we need to pass in the workspace and then use workspace.KuberneteContext() to look up the correct context. ## Type of change This pull request fixes a bug in Radius and has an approved issue (issue link required). Fixes: radius-project#5698 --------- Signed-off-by: Josh <josh@liveoak.ws>
…ius-project#7154) Signed-off-by: Josh <josh@liveoak.ws> # Description in order for the non current context to be used by ValidateNamespaces so that it can create namespaces in the workspaces kubernetes context we need to pass in the workspace and then use workspace.KuberneteContext() to look up the correct context. ## Type of change This pull request fixes a bug in Radius and has an approved issue (issue link required). Fixes: radius-project#5698 --------- Signed-off-by: Josh <josh@liveoak.ws> Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: Josh josh@liveoak.ws
Description
in order for the non current context to be used by ValidateNamespaces so that it can create namespaces in the workspaces kubernetes context we need to pass in the workspace and then use workspace.KuberneteContext() to look up the correct context.
Type of change
This pull request fixes a bug in Radius and has an approved issue (issue link required).
Fixes: #5698