Had to change all the names in the build script to be simple-file-manager-for-amazon-efs from efs_file_manager also in the two CloudFormation templates for SB pipe
Added CFN Nag Meta data tags into external_resources.json also I modified the build-s3-dist.sh just to not use AWS s3 Sync when running through SB pipe
Adding buildspec.yml file so that the SB pipe can call our build script. Tested that out
Adding ignore fields to viperlightignore so SB pipe builds
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Just to note I tested this in the SB pipe after build, and also tested on a local bucket in my account to make sure things can build in both areas fine! 👍
Issue #, if available: Making a ton of changes so it works in the SB pipe. Closing out these tickets.
I also tested building locally, and sending to buckets on my AWS account. You can see changes I made in the diff. Thanks
https://github.com/aws-samples/simple-file-manager-for-amazon-efs/issues/135 https://github.com/aws-samples/simple-file-manager-for-amazon-efs/issues/134 https://github.com/aws-samples/simple-file-manager-for-amazon-efs/issues/133
Description of changes:
Had to change all the names in the build script to be simple-file-manager-for-amazon-efs from efs_file_manager also in the two CloudFormation templates for SB pipe
Added CFN Nag Meta data tags into external_resources.json also I modified the build-s3-dist.sh just to not use AWS s3 Sync when running through SB pipe
Adding buildspec.yml file so that the SB pipe can call our build script. Tested that out
Adding ignore fields to viperlightignore so SB pipe builds
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.