Skip to content

Individual Step Function Deploy #561

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

Closed
jappurohit041 opened this issue Apr 14, 2023 · 1 comment
Closed

Individual Step Function Deploy #561

jappurohit041 opened this issue Apr 14, 2023 · 1 comment

Comments

@jappurohit041
Copy link
Contributor

This is a Feature Proposal

Individual Step Function Deploy

This document outlines the process for adding the individual step function deploy feature to a plugin.

Background

Step functions are a powerful tool for building serverless workflows. They allow you to orchestrate multiple AWS services into a cohesive workflow. However, deploying step functions can be challenging. AWS provides a web-based interface for building and testing step functions, but deploying them requires the use of the AWS CLI or SDK. This can be complex and error-prone, especially when you have multiple step functions to deploy.

Problem

The current plugin for deploying step functions does not allow for individual step function deployment. This means that all step functions in a stack must be deployed at once, even if only one has changed. This can be time-consuming and can increase the risk of errors.

Solution

The solution is to add an individual step function deploy feature to the plugin. This feature will allow developers to deploy a single step function without having to deploy the entire stack. This will save time and reduce the risk of errors.

Implementation

To implement the individual step function deploy feature, the following steps should be taken:

  1. Add a new command to the plugin that allows for the deployment of a single step function. This command should take the name of the step function as a parameter.
  2. Modify the existing deploy command to allow for the deployment of a step functions at once. This commands take a name of step function as a parameter.
  3. Sample argument:
serverless deploy stepf --name *Step_Machine_Name*

Conclusion

By adding the individual step function deploy feature to the plugin, developers will have greater control over the deployment of their step functions. This will save time and reduce the risk of errors.

@jappurohit041
Copy link
Contributor Author

#562

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant