Allow specifying which user the stack files should belong to #83
Conversation
This file contains 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
|
Fix Eslint errors! |
There was a problem hiding this comment.
Do we want to change the owner if the stack already existed, potentially with different owner?
There was a problem hiding this comment.
Maybe nitpicky but what happens when we create a new stack and writeFileSync throws an error (not enough space)? Arn't we left with a new stack folder still owned by root?
|
can this be merged soon please? |
|
Hi, any news for a merge timeline ? This would be amazing to not create stack with terminal every time ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR addresses #80 where any new stacks are created under the roots ownership