Skip to content
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

Enable --environment flag for rad app CLI commands #8222

Open
1 task
willtsai opened this issue Jan 10, 2025 · 4 comments
Open
1 task

Enable --environment flag for rad app CLI commands #8222

willtsai opened this issue Jan 10, 2025 · 4 comments
Labels
feature This issue describes a feature request in Radius triaged This issue has been reviewed and triaged

Comments

@willtsai
Copy link
Contributor

willtsai commented Jan 10, 2025

Overview of feature request

Previously, the -e or --environment flag was available in the rad app graph -e command, but the flag did not have any effect on the operation and was thus removed as a part of Issue #7507 (PR #8099).

Since there might be some cases where it would be useful in the CLI to execute operations against an app for a specific environment, this feature request is to enable the passing of an --environment flag into the rad app * family of commands. e.g. As a user, I'm currently under the production environment in my current CLI context, but I would like to view the app graph for my application that has been deployed into the dev environment as well without having to change my CLI context.

Acceptance criteria

  1. The following CLI commands allow for specifying an optional --environment or -e flag that prompts the CLI to execute the command for the environment specified by the user:
  • rad application delete
  • rad application graph
  • rad application list
  • rad application show
  • rad application status
  1. If the --environment or -e flag is not specified, then the CLI executes the command for the current environment context of the CLI (this should be the existing behavior).

Additional context

No response

Would you like to support us?

  • Yes, I would like to support you

AB#14041

@willtsai willtsai added the feature This issue describes a feature request in Radius label Jan 10, 2025
@radius-triage-bot
Copy link

👋 @willtsai Thanks for filing this feature request.

A project maintainer will review this feature request and get back to you soon.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

@superbeeny
Copy link
Contributor

Could this be considered as a first step towards multi-tenancy and multi-cluster support?

@willtsai willtsai added the triaged This issue has been reviewed and triaged label Feb 3, 2025
@radius-triage-bot
Copy link

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

@superbeeny
Copy link
Contributor

I do like this idea, much like we can add a -g or --group flag it would be nice to be able to specify and environment without having to switch to the target environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature This issue describes a feature request in Radius triaged This issue has been reviewed and triaged
Projects
None yet
Development

No branches or pull requests

2 participants