You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixed deployment of aws resources if a pipeline name is not specified (aws#117)
Fixed deployment of aws resources which would fail if option `--create-update-aws-pipeline-name` was not specified:
* corrected mismatch of resolver schema file name when creating the lambda zip file by passing the generated schema file name to the function which is creating the zip file
* changed the output file prefix to only have the `.output` suffix if there is no discovered graph name
* changed App Sync Function and DataSource resource names to replace any dashes `-` with underscores as dashes are not allowed (but can be present in Neptune db/graph names)
* added integration tests to validate that correct output files and zip file content are created if no pipeline name is provided
Other minor changes:
* changed file error logging to include the `error.message` as the error message was output to console but missing from the file
* added validation of output folder files to CDK integration tests
* modified affected test cases to have descriptive file names and output folders
0 commit comments