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
Describe the bug
The app is published in production workspace, On modifying any assets or actions and re-executing command "aio app deploy --force-deploy" will result in error though the changes are updated.
To Reproduce
Steps to reproduce the behavior:
Create and publish the app.
Update the actions or any web assets
Deploy the app using "aio app deploy" or aio app deploy --force-deploy
Expected behavior
The deployment shouldn't throw an error as we are not updating the app endpoints in app registry
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Windows
Browser: Chrome
Node : 20.9.0
npm : 10.1.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Yeah this error is coming from the Developer Console. To avoid these errors, I'm thinking we skip publishing if --force-deploy is specified and the user is working in a published prod app. Also make --force-deploy mutually exclusive with --publish and --force-publish
Describe the bug
The app is published in production workspace, On modifying any assets or actions and re-executing command "aio app deploy --force-deploy" will result in error though the changes are updated.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The deployment shouldn't throw an error as we are not updating the app endpoints in app registry
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: