-
Notifications
You must be signed in to change notification settings - Fork 74
Description
- ricecooker version: develop branch
Summary
It appears that --deploy no longer does anything. It is also a prerequisite for also passing --publish. On Studio, we re-architected how the deploy process functions to utilize change events. Publishing already uses the same change event mechanism. The change event mechanism would require polling of Studio in order to determine if those change events are applied.
Additionally, --deploy maps to stage in the code, and is confusing because there was at one point a --stage arg that is now deprecated and is the default behavior.
Desired behavior
Reviewing a staged channel on Studio before deploying it sounds like the ideal workflow that we want to encourage, but we may wish to keep this ability within ricecooker. That means we either need to:
- remove the arguments and their functionality, and update the documentation, or
- update their functionality to function with changes made to Studio, allowing these to process the operations in change events
Reference: learningequality/studio#3997