-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Enhancement] Add support for specifying organization in the create project command. #48
Labels
Milestone
Comments
ankitrgadiya
pushed a commit
that referenced
this issue
Nov 14, 2022
…ject command (#54) The `project create` command now accepts `--organization` flag. It accepts both name and organization GUID. This allows user to create a project in other organizations user is part of but is not currently operating under. If this flag is not provided, then organization of the currently selected project will be used. User can check the current project through multiple ways: 1. `project list` command highlights the current project in green color. 2. `shell` command uses project name as the shell prompt. 3. The config file saves the `project_id` variable as well. Resolves #48
Resolved in #54 |
rr-github-ci-user
pushed a commit
that referenced
this issue
Nov 23, 2022
# [0.5.0](v0.4.0...v0.5.0) (2022-11-23) ### Bug Fixes * **apply:** fixes apply without workers flag behaviour ([a6b1d71](a6b1d71)) * **apply:** fixes guid_functor for network ([0831a0c](0831a0c)) * **config:** new_client without project now does not read project from config ([7c2c5fd](7c2c5fd)) * **package:** fixes several issues with rending packages from apply manifests ([c1acc1e](c1acc1e)) ### Features * **project:** adds support for specifying organization in create project command ([#54](#54)) ([39f19b6](39f19b6)), closes [#48](#48)
🎉 This issue has been resolved in version 0.5.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
ayushgaud
pushed a commit
that referenced
this issue
Dec 23, 2022
# [0.5.0](v0.4.0...v0.5.0) (2022-11-23) ### Bug Fixes * **apply:** fixes apply without workers flag behaviour ([a6b1d71](a6b1d71)) * **apply:** fixes guid_functor for network ([0831a0c](0831a0c)) * **config:** new_client without project now does not read project from config ([7c2c5fd](7c2c5fd)) * **package:** fixes several issues with rending packages from apply manifests ([c1acc1e](c1acc1e)) ### Features * **project:** adds support for specifying organization in create project command ([#54](#54)) ([39f19b6](39f19b6)), closes [#48](#48)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The
project create
sub-command is used to create the new project. It uses the client initiazed to create a new project which is inherently associated with the currently selected organization.After the release of users being part of multiple organizations, this also needs to support specifying the organization under which user wants to create the project.
┆Issue is synchronized with this Wrike task
The text was updated successfully, but these errors were encountered: