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
Is your feature request related to a problem? Please describe.
As of today, aio app deploy builds and deploys the whole app. aio app deploy --skip-build only deploys the app. aio app deploy --skip-deploy only builds the app.
This is confusing for users and we should provide a more obvious way to handle build and deploy separately. This can be very useful for CI/CD and other automation use-cases.
Describe the solution you'd like
Proposal:
aio app build builds the whole app aio app build -a|--action=action builds an action aio app build --all-actions builds all actions aio app build -s|--static builds the SPA
aio app deploy behaves as of today if there's no build. aio app deploy just deploys if there's a build. aio app deploy -b|--build forces the build before the deploy (do we even need more fine-grained based?)
The text was updated successfully, but these errors were encountered:
meryllblanchet
changed the title
Build & Deploy should be possible as distinct CLI commands
Build & Deploy should be available as distinct CLI commands
Aug 31, 2020
Is your feature request related to a problem? Please describe.
As of today,
aio app deploy
builds and deploys the whole app.aio app deploy --skip-build
only deploys the app.aio app deploy --skip-deploy
only builds the app.This is confusing for users and we should provide a more obvious way to handle build and deploy separately. This can be very useful for CI/CD and other automation use-cases.
Describe the solution you'd like
Proposal:
aio app build
builds the whole appaio app build -a|--action=action
builds an actionaio app build --all-actions
builds all actionsaio app build -s|--static
builds the SPAaio app deploy
behaves as of today if there's no build.aio app deploy
just deploys if there's a build.aio app deploy -b|--build
forces the build before the deploy (do we even need more fine-grained based?)The text was updated successfully, but these errors were encountered: