chore: throw more descriptive error when failing to create output directory#18296
Merged
mergify[bot] merged 5 commits intoaws:masterfrom Mar 30, 2022
Merged
chore: throw more descriptive error when failing to create output directory#18296mergify[bot] merged 5 commits intoaws:masterfrom
mergify[bot] merged 5 commits intoaws:masterfrom
Conversation
|
|
Contributor
|
Title does not follow the guidelines of Conventional Commits. Please adjust title before merge. |
rix0rrr
previously approved these changes
Mar 30, 2022
TheRealAmazonKendra
approved these changes
Mar 30, 2022
Contributor
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Collaborator
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Contributor
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
StevePotter
pushed a commit
to StevePotter/aws-cdk
that referenced
this pull request
Apr 27, 2022
…ectory (aws#18296) I passed a `--output` to the CDK that was `/public/something/or/other`, on a system with no `/public`, and then forgot about it. I was presented with the head-scratch-inducing failure message: ``` ENOENT: no such file or directory, mkdir '/public' Error: ENOENT: no such file or directory, mkdir '/public' ``` This should improve the error so that some reference is made to why the CDK expects or desires this path to exist (and remind me that in fact I told it to go there). ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
I passed a
--outputto the CDK that was/public/something/or/other, on a system with no/public, and then forgot about it. I was presented with the head-scratch-inducing failure message:This should improve the error so that some reference is made to why the CDK expects or desires this path to exist (and remind me that in fact I told it to go there).
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license