-
Notifications
You must be signed in to change notification settings - Fork 894
feat: Add "coder projects create" command #246
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
7167fa0
Refactor parameter parsing to return nil values if none computed
kylecarbs 65380db
Refactor parameter to allow for hiding redisplay
kylecarbs 94eb484
Refactor parameters to enable schema matching
kylecarbs a6ce22d
Refactor provisionerd to dynamically update parameter schemas
kylecarbs e53f0be
Refactor job update for provisionerd
kylecarbs 4466836
Handle multiple states correctly when provisioning a project
kylecarbs 8fe05d6
Add project import job resource table
kylecarbs 79a56b6
Basic creation flow works!
kylecarbs dc86c0e
Create project fully works!!!
kylecarbs bff96b6
Only show job status if completed
kylecarbs 8766a33
Add create workspace support
kylecarbs aac220f
Replace Netflix/go-expect with ActiveState
kylecarbs c493bf9
Fix linting errors
kylecarbs 485c07b
Use forked chzyer/readline
kylecarbs b5a774a
Add create workspace CLI
kylecarbs d2cbf36
Add CLI test
kylecarbs a8d00d8
Move jobs to their own APIs
kylecarbs 9c7746f
Merge branch 'main' into createproject
kylecarbs e4770bb
Remove go-expect
kylecarbs c6cee94
Fix requested changes
kylecarbs f9814be
Skip workspacecreate test on windows
kylecarbs File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Fix linting errors
- Loading branch information
commit c493bf9da0a80112ca4a79a3991c97b9c95624aa
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should have a check here to sanitize the
header.Name
- making sure we can't specify paths like..
that might move up the filesystem. There might be a vulnerability where you could construct atar
that has a header with improper paths (like../../
) - and let you write a file over an existing file.This would be bad, for example, if a malicious actor could write over a critical config file, a binary (ie, they overwrite our
provisionerd
with a malicious version that uploads secrets).Kind of a similar to the example called out here: securego/gosec#439 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, and we handle this from provisionerd. But I didn't feel it was necessary for
clitest
.We should abstract the tar/untar logic out so it's in one place, then add tests for that specific functionality.