twilio-proserv-flex-project-template
kandi X-RAY | twilio-proserv-flex-project-template Summary
kandi X-RAY | twilio-proserv-flex-project-template Summary
twilio-proserv-flex-project-template is a TypeScript library. twilio-proserv-flex-project-template has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.
At the root of the repository you will find the following packages. these packages are coupled together to provide a means of versioning these artifacts together, providing a robust method for building a release pipeline across multiple environments. flex-config: this package manages a json artifact that can be used to version configuration elements on a per-twilio-account basis. We can think of this as allowing us to configure, dev, qa, test, production or any other environments indivdually. This configuration relates specifically to the the configuration for flex discussed here and works by injecting the custom object into ui_attributes within the flex configuration object. The plugin is then able to reference these variables. The first example being, hosting the domain name of the associated serverless-functions. infra-as-code: this package is a legacy package of a previous initiative to leverage pulumi to manage twilio configuration artifacts such as taskrouter entities. This package is a functional methodology and was setup to represent a typicaly vanilla flex account thats just been initialized. This package has not been maintained as the intention is to move towards a similar solution using the terraform provider, however what has been setup and used before is available for anyone looking to use it for immediate needs. More details on how to use this can be found here. Currently there are no dependencies in this package that need to be used and is here only for reference. Feel free to remove this if not utilized. plugin-flex-ts-template: this package is the actual flex plugin and a structure is already laid out that makes it a lot easier to work in a disributed development model. More details of the package structure are discussed over here but just now the imporant thing to understand is that the plugin has a library of examples that can be turned on or off, or if desired can be removed completely with little overhead. The utilities in this package are designed around the associated serverless-functions and leverage the associated flex-config. plugin-flex-ts-template-v2: this package is identical in purpose tot he plugin-flex-ts-template except its intended for flex v2 projects. This package is still a work in progress as we migrate the feature libraries over. It is functional as a package structure though. The intention is when kicking off a project the owner would fork the repository then delete the plugin version they are not using. serverless-functions: this package manages the serverless functions that the plugin-flex-ts-template is dependent on. In this package there are a suite of services already available to use, some of which are simply wrappers around existing twilio APIs but with added resiliancy around retrying given configurable parameters. These retry mechanisms are particularly useful when a twilio function needs to orchestrate multiple twilio APIs to perform an overall operation. It should be noted twilio functions still have a maximum runtime and therefore careful consideration of retries should be employed for each use case. This does however provided improved resiliency and performance when 429s, 412s or 503s occur. .github lastly this package manages the github action workflows - with one example being setup for a dev account where this template is maintained. Upon commits to main; flex-config, plugin-flex-ts-template and serverless-functions are all deployed on the associated environment, as controlled by the environment variables in github actions. The underly scripts can easily be used in alternative release management tools.
At the root of the repository you will find the following packages. these packages are coupled together to provide a means of versioning these artifacts together, providing a robust method for building a release pipeline across multiple environments. flex-config: this package manages a json artifact that can be used to version configuration elements on a per-twilio-account basis. We can think of this as allowing us to configure, dev, qa, test, production or any other environments indivdually. This configuration relates specifically to the the configuration for flex discussed here and works by injecting the custom object into ui_attributes within the flex configuration object. The plugin is then able to reference these variables. The first example being, hosting the domain name of the associated serverless-functions. infra-as-code: this package is a legacy package of a previous initiative to leverage pulumi to manage twilio configuration artifacts such as taskrouter entities. This package is a functional methodology and was setup to represent a typicaly vanilla flex account thats just been initialized. This package has not been maintained as the intention is to move towards a similar solution using the terraform provider, however what has been setup and used before is available for anyone looking to use it for immediate needs. More details on how to use this can be found here. Currently there are no dependencies in this package that need to be used and is here only for reference. Feel free to remove this if not utilized. plugin-flex-ts-template: this package is the actual flex plugin and a structure is already laid out that makes it a lot easier to work in a disributed development model. More details of the package structure are discussed over here but just now the imporant thing to understand is that the plugin has a library of examples that can be turned on or off, or if desired can be removed completely with little overhead. The utilities in this package are designed around the associated serverless-functions and leverage the associated flex-config. plugin-flex-ts-template-v2: this package is identical in purpose tot he plugin-flex-ts-template except its intended for flex v2 projects. This package is still a work in progress as we migrate the feature libraries over. It is functional as a package structure though. The intention is when kicking off a project the owner would fork the repository then delete the plugin version they are not using. serverless-functions: this package manages the serverless functions that the plugin-flex-ts-template is dependent on. In this package there are a suite of services already available to use, some of which are simply wrappers around existing twilio APIs but with added resiliancy around retrying given configurable parameters. These retry mechanisms are particularly useful when a twilio function needs to orchestrate multiple twilio APIs to perform an overall operation. It should be noted twilio functions still have a maximum runtime and therefore careful consideration of retries should be employed for each use case. This does however provided improved resiliency and performance when 429s, 412s or 503s occur. .github lastly this package manages the github action workflows - with one example being setup for a dev account where this template is maintained. Upon commits to main; flex-config, plugin-flex-ts-template and serverless-functions are all deployed on the associated environment, as controlled by the environment variables in github actions. The underly scripts can easily be used in alternative release management tools.
Support
Quality
Security
License
Reuse
Support
twilio-proserv-flex-project-template has a low active ecosystem.
It has 11 star(s) with 5 fork(s). There are 7 watchers for this library.
It had no major release in the last 6 months.
twilio-proserv-flex-project-template has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of twilio-proserv-flex-project-template is current.
Quality
twilio-proserv-flex-project-template has no bugs reported.
Security
twilio-proserv-flex-project-template has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
twilio-proserv-flex-project-template does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
twilio-proserv-flex-project-template releases are not available. You will need to build from source code and install.
Installation instructions are available. Examples and code snippets are not available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of twilio-proserv-flex-project-template
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of twilio-proserv-flex-project-template
twilio-proserv-flex-project-template Key Features
No Key Features are available at this moment for twilio-proserv-flex-project-template.
twilio-proserv-flex-project-template Examples and Code Snippets
No Code Snippets are available at this moment for twilio-proserv-flex-project-template.
Community Discussions
No Community Discussions are available at this moment for twilio-proserv-flex-project-template.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install twilio-proserv-flex-project-template
cd serverless-functions && twilio serverless:deploy. cd flex-config && npm run deploy:dev. cd plugin-flex-ts-template && twilio flex:plugins:start.
Clone the repository git clone https://github.com/twilio-professional-services/twilio-proserv-flex-project-template.git
cd into the repository and execute (this installs all sub-project dependencies and creates two new .env files for the next step) npm install
Edit both serverless-functions/.env and flex-config/.env
Review the SIDs in the .env files and update with the appropriate ones from your own account. If you are using any features from the feature library, ensure you have read the appropriate readme for given feature and any dependencies that those features require are setup. All variables under general should be set and if no features are being used, the rest can be ignored.
Deploy serverless functions into your account cd serverless-functions && twilio serverless:deploy
Copy the domain name from the deployment details in step 4 and update flex-config/ui_attributes.dev.json
Ensure the proper destination account is active in the twilio cli twilio profiles:list
With selected account, deploy the configuration cd flex-config && npm run deploy:dev
Begin local run of flex plugin cd plugin-flex-ts-template && twilio flex:plugins:start
Clone the repository git clone https://github.com/twilio-professional-services/twilio-proserv-flex-project-template.git
cd into the repository and execute (this installs all sub-project dependencies and creates two new .env files for the next step) npm install
Edit both serverless-functions/.env and flex-config/.env
Review the SIDs in the .env files and update with the appropriate ones from your own account. If you are using any features from the feature library, ensure you have read the appropriate readme for given feature and any dependencies that those features require are setup. All variables under general should be set and if no features are being used, the rest can be ignored.
Deploy serverless functions into your account cd serverless-functions && twilio serverless:deploy
Copy the domain name from the deployment details in step 4 and update flex-config/ui_attributes.dev.json
Ensure the proper destination account is active in the twilio cli twilio profiles:list
With selected account, deploy the configuration cd flex-config && npm run deploy:dev
Begin local run of flex plugin cd plugin-flex-ts-template && twilio flex:plugins:start
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page