The idea came from the reason to create an .env file for client project, the variables are aws cloud formation exports.
for example you just created cloudformation stack for the backend of your application, and you exported DEV-APIGATEWAY-URL.
with this package you can now create .env file in your client application and import this variable before build.
//.env.template
REACT_APP_APPLICATION_URL=DEV-APIGATEWAY-URL // you can use --prefix DEV- and then just put APIGATEWAY-URL
//package.json
"pre-build":"cfexport compile -v --file \"./.env.template\" --region us-east-1 --output \"./.env\" --format \".env\""
npm i -g cfexport
cfexport compile -v --file "./.env.template.json" --region us-east-1 --output "./.env.json" --format "json"
cfexport compile -v --file "./.env.template" --region us-east-1 --output "./.env" --format ".env"
to make the call to aws to get the exports you need to have aws credential configure (by env or file, see aws sdk docs for more info) make sure you have the access right to do: cloudformation:ListExports on Resource *
FAQs
Create configuration file from cloudformation exports.
The npm package cfexport receives a total of 0 weekly downloads. As such, cfexport popularity was classified as not popular.
We found that cfexport demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Company News
Socket is joining the OpenJS Security Stewardship Program to fund Node.js vulnerability research, maintainer remediation, and security releases.
Security News
Two compromised GitHub Actions were re-enabled with malicious tags intact, exposing thousands of downstream repositories to Mini Shai-Hulud.
Research
/Security News
A malicious Firefox extension fetches its payload after installation to evade detection, steal Google session cookies, and automate account takeover.