fix(cli): add noUpdateBackend cli argument for pull and add headless pull sample #8804
Conversation
…pull sample Adds an option to the cli when using the pull option that lets you specify not to update the backend to be able to generate aws-exports.js. This is an alternative to yes option which defaults to modifying the backend and is good for frontend custom CICD deployments. re aws-amplify#7468
Codecov Report
@@ Coverage Diff @@
## master #8804 +/- ##
=======================================
Coverage 57.20% 57.20%
=======================================
Files 757 757
Lines 42243 42243
Branches 8659 8659
=======================================
Hits 24166 24166
Misses 17263 17263
Partials 814 814 Continue to review full report at Codecov.
|
siegerts
added
the
first-time-contributor
|
Hey @awsaxeman, would you be interested in continuing to work on this PR? If so, please rebase this onto dev by running |
|
We haven't heard back from you so we are going to close this pull request. If you are interested in pursuing it in the future, please reopen it. |
|
Hello @evcodes I've re-submitted the changes in this PR here: #13434 |
Description of changes
Adds an option to the cli when using the pull option that lets you specify not to update the
backend (--noUpdateBackend) to be able to generate aws-exports.js. This is an alternative to --yes option which defaults
to modifying the backend and is good for frontend custom CICD deployments.
Issue #, if available
re #7468
Description of how you validated changes
Tested with pull script and was able to pull down an existing amplify app to an empty project directory.
Checklist
yarn testpassesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.