New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compose CLI Command Schema #12389
Comments
If we do want to be able to perform more granular commands in a Service from a Compose file, this seems like it fits nicely without changing the UX. # In serverless.yml
serverless deploy function -f myApi # In serverless-compose.yml
serverless service-a deploy function -f myApi |
100% @ac360 I should have clarified better, but my intention was to not change how framework services work. So your examples are exactly what I intended. The examples currently are more for Extensions and Compose in general. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Use case description
Framework currently follows a command format in the CLI where the action is the first action followed by an optional resource type and then whatever flags the command may require. However as new features such as Compose were added, we did not adhere to this standard and instead introduced further fragmentation where you would run Compose commands with different syntax.
In V4, we are going to keep the framework syntax as is, there will be no changes there. However we are going to revise the CLI command standards for Compose & Extensions.
We are going to introduce the following basic schema,
The goal is to have Compose and EXT adhere to this model going forward.
Examples
serverless-compose.yml
Framework Service serverless.yml
Extension Service serverless.yml
So with these files we can then run commands in the following ways,
Run Deploy on a specific service in Compose
Run a command on a specific extension instance in Compose
Run Deploy function on a specific framework service in Compose
Proposed solution (optional)
No response
The text was updated successfully, but these errors were encountered: