Deploy service stack - Notifications: Difference between revisions

From Izara Wiki
Jump to navigation Jump to search
(Created page with "= Inject seed data after deploy = If want to run seeddata immediately after deploying each service, should run sequential services as follows: # MsgCfgMng # ActivitySwitchbo...")
 
No edit summary
 
Line 1: Line 1:
= Deploy instructions per service =
== Message Config Manager (MsgCfgMng) ==
# Clone project and npm install
# cd \MsgCfgMng\resource
# npm install
# cd \MsgCfgMng\app
# npm install
# modify /MsgCfgMng/config/serverless.config.yml
#* Prefix (optional) 
#* Stage (optional)
#* ...
#* authorizer_appLevel(hardcode): "arn:aws:lambda:us-east-2:468568093265:function:{func_name}"
# cd \MsgCfgMng\resource 
# serverless deploy 
# cd \MsgCfgMng\app 
# serverless deploy
# modify app/src/initial_setup/config
# Edit/Add seed data to initial_setup
# re-deploy
# In AWS console invoke initial_setup lambda (Services > Lambda > MsgCfgMng...initialSetup)
# Click "test" for invoke
== ActivitySwitchboard ==
# Clone project and npm install
# cd \ActivitySwitchboard\resource
# npm install
# cd \ActivitySwitchboard\app
# npm install
# modify /ActivitySwitchboard/config/serverless.config.yml
#* Prefix (optional) 
#* Stage (optional)
#* ...
#* authorizer_appLevel(hardcode): "arn:aws:lambda:us-east-2:468568093265:function:{func_name}"
# cd \ActivitySwitchboard\resource 
# serverless deploy 
# cd \ActivitySwitchboard\app 
# serverless deploy
# modify app/src/initial_setup/config
# Edit/Add seed data to initial_setup
# re-deploy
# In AWS console invoke initial_setup lambda (Services > Lambda > ActivitySwitchboard...initialSetup)
# Click "test" for invoke
For client:
# update client /src/config.js > apiGateway endpoint
#* Get endpoint: Services > APIs > ActivitySwitchboard... > stages > ... > Invoke URL: https://{api code}.execute-api.{region}.amazonaws.com/{stage}
#* Put endpoint: Test-request-web service > /src/config.js > apiGateway endpoint > ACTIVITYSWITCHBOARD: xxxxxx
== Notification Manager(NotificationMgr) ==
# Clone project and npm install
# cd \NotificationMgr\resource
# npm install
# cd \NotificationMgr\app
# npm install
# modify /NotificationMgr/config/serverless.config.yml
#* Prefix (optional) 
#* Stage (optional)
#* ...
#* authorizer_appLevel(hardcode): "arn:aws:lambda:us-east-2:468568093265:function:{func_name}"
# cd \NotificationMgr\resource 
# serverless deploy 
# cd \NotificationMgr\app 
# serverless deploy
# modify app/src/initial_setup/config
# Edit/Add seed data to initial_setup
# re-deploy
# In AWS console invoke initial_setup lambda (Services > Lambda > NotificationMgr...initialSetup)
# Click "test" for invoke
For client:
# update client /src/config.js > apiGateway endpoint
#* Get endpoint: Services > APIs > NotificationMgr... > stages > ... > Invoke URL: https://{api code}.execute-api.{region}.amazonaws.com/{stage}
#* Put endpoint: Test-request-web service > /src/config.js > apiGateway endpoint > NOTIFICATIONMGR: xxxxxx
== Contact Method(ContactMethodEmail) ==
# Clone project and npm install
# cd \ContactMethodEmail\resource
# npm install
# cd \ContactMethodEmail\app
# npm install
# modify /ContactMethodEmail/config/serverless.config.yml
#* Prefix (optional) 
#* Stage (optional)
#* ...
#* authorizer_appLevel(hardcode): "arn:aws:lambda:us-east-2:468568093265:function:{func_name}"
# cd \ContactMethodEmail\resource 
# serverless deploy 
# cd \ContactMethodEmail\app 
# serverless deploy
# modify app/src/initial_setup/config
# Edit/Add seed data to initial_setup
# re-deploy
# In AWS console invoke initial_setup lambda (Services > Lambda > ContactMethodEmail...initialSetup)
# Click "test" for invoke
For client:
# update client /src/config.js > apiGateway endpoint
#* Get endpoint: Services > APIs > ContactMethodEmail... > stages > ... > Invoke URL: https://{api code}.execute-api.{region}.amazonaws.com/{stage}
#* Put endpoint: Test-request-web service > /src/config.js > apiGateway endpoint > CONTACTMETHODEMAIL: xxxxxx
== User Contact Manager(UsrCntMgr) ==
# Clone project and npm install
# cd \UsrCntMgr\resource
# npm install
# cd \UsrCntMgr\app
# npm install
# modify /UsrCntMgr/config/serverless.config.yml
#* Prefix (optional) 
#* Stage (optional)
#* ...
#* authorizer_appLevel(hardcode): "arn:aws:lambda:us-east-2:468568093265:function:{func_name}"
# cd \UsrCntMgr\resource 
# serverless deploy 
# cd \UsrCntMgr\app 
# serverless deploy
# modify app/src/initial_setup/config
# Edit/Add seed data to initial_setup
# re-deploy
# In AWS console invoke initial_setup lambda (Services > Lambda > UsrCntMgr...initialSetup)
# Click "test" for invoke
For client:
# update client /src/config.js > apiGateway endpoint
#* Get endpoint: Services > APIs > UsrCntMgr... > stages > ... > Invoke URL: https://{api code}.execute-api.{region}.amazonaws.com/{stage}
#* Put endpoint: Test-request-web service > /src/config.js > apiGateway endpoint > USRCNTMGR: xxxxxx
= Inject seed data after deploy =
= Inject seed data after deploy =


If want to run seeddata immediately after deploying each service, should run sequential services as follows:
If want to run seeddata immediately after deploying each service, should sequentially deploy services as follows:


# MsgCfgMng
# MsgCfgMng

Latest revision as of 13:53, 17 August 2021

Deploy instructions per service

Message Config Manager (MsgCfgMng)

  1. Clone project and npm install
  2. cd \MsgCfgMng\resource
  3. npm install
  4. cd \MsgCfgMng\app
  5. npm install
  6. modify /MsgCfgMng/config/serverless.config.yml
    • Prefix (optional)
    • Stage (optional)
    • ...
    • authorizer_appLevel(hardcode): "arn:aws:lambda:us-east-2:468568093265:function:{func_name}"
  7. cd \MsgCfgMng\resource
  8. serverless deploy
  9. cd \MsgCfgMng\app
  10. serverless deploy
  11. modify app/src/initial_setup/config
  12. Edit/Add seed data to initial_setup
  13. re-deploy
  14. In AWS console invoke initial_setup lambda (Services > Lambda > MsgCfgMng...initialSetup)
  15. Click "test" for invoke

ActivitySwitchboard

  1. Clone project and npm install
  2. cd \ActivitySwitchboard\resource
  3. npm install
  4. cd \ActivitySwitchboard\app
  5. npm install
  6. modify /ActivitySwitchboard/config/serverless.config.yml
    • Prefix (optional)
    • Stage (optional)
    • ...
    • authorizer_appLevel(hardcode): "arn:aws:lambda:us-east-2:468568093265:function:{func_name}"
  7. cd \ActivitySwitchboard\resource
  8. serverless deploy
  9. cd \ActivitySwitchboard\app
  10. serverless deploy
  11. modify app/src/initial_setup/config
  12. Edit/Add seed data to initial_setup
  13. re-deploy
  14. In AWS console invoke initial_setup lambda (Services > Lambda > ActivitySwitchboard...initialSetup)
  15. Click "test" for invoke

For client:

  1. update client /src/config.js > apiGateway endpoint
    • Get endpoint: Services > APIs > ActivitySwitchboard... > stages > ... > Invoke URL: https://{api code}.execute-api.{region}.amazonaws.com/{stage}
    • Put endpoint: Test-request-web service > /src/config.js > apiGateway endpoint > ACTIVITYSWITCHBOARD: xxxxxx

Notification Manager(NotificationMgr)

  1. Clone project and npm install
  2. cd \NotificationMgr\resource
  3. npm install
  4. cd \NotificationMgr\app
  5. npm install
  6. modify /NotificationMgr/config/serverless.config.yml
    • Prefix (optional)
    • Stage (optional)
    • ...
    • authorizer_appLevel(hardcode): "arn:aws:lambda:us-east-2:468568093265:function:{func_name}"
  7. cd \NotificationMgr\resource
  8. serverless deploy
  9. cd \NotificationMgr\app
  10. serverless deploy
  11. modify app/src/initial_setup/config
  12. Edit/Add seed data to initial_setup
  13. re-deploy
  14. In AWS console invoke initial_setup lambda (Services > Lambda > NotificationMgr...initialSetup)
  15. Click "test" for invoke

For client:

  1. update client /src/config.js > apiGateway endpoint
    • Get endpoint: Services > APIs > NotificationMgr... > stages > ... > Invoke URL: https://{api code}.execute-api.{region}.amazonaws.com/{stage}
    • Put endpoint: Test-request-web service > /src/config.js > apiGateway endpoint > NOTIFICATIONMGR: xxxxxx

Contact Method(ContactMethodEmail)

  1. Clone project and npm install
  2. cd \ContactMethodEmail\resource
  3. npm install
  4. cd \ContactMethodEmail\app
  5. npm install
  6. modify /ContactMethodEmail/config/serverless.config.yml
    • Prefix (optional)
    • Stage (optional)
    • ...
    • authorizer_appLevel(hardcode): "arn:aws:lambda:us-east-2:468568093265:function:{func_name}"
  7. cd \ContactMethodEmail\resource
  8. serverless deploy
  9. cd \ContactMethodEmail\app
  10. serverless deploy
  11. modify app/src/initial_setup/config
  12. Edit/Add seed data to initial_setup
  13. re-deploy
  14. In AWS console invoke initial_setup lambda (Services > Lambda > ContactMethodEmail...initialSetup)
  15. Click "test" for invoke

For client:

  1. update client /src/config.js > apiGateway endpoint
    • Get endpoint: Services > APIs > ContactMethodEmail... > stages > ... > Invoke URL: https://{api code}.execute-api.{region}.amazonaws.com/{stage}
    • Put endpoint: Test-request-web service > /src/config.js > apiGateway endpoint > CONTACTMETHODEMAIL: xxxxxx

User Contact Manager(UsrCntMgr)

  1. Clone project and npm install
  2. cd \UsrCntMgr\resource
  3. npm install
  4. cd \UsrCntMgr\app
  5. npm install
  6. modify /UsrCntMgr/config/serverless.config.yml
    • Prefix (optional)
    • Stage (optional)
    • ...
    • authorizer_appLevel(hardcode): "arn:aws:lambda:us-east-2:468568093265:function:{func_name}"
  7. cd \UsrCntMgr\resource
  8. serverless deploy
  9. cd \UsrCntMgr\app
  10. serverless deploy
  11. modify app/src/initial_setup/config
  12. Edit/Add seed data to initial_setup
  13. re-deploy
  14. In AWS console invoke initial_setup lambda (Services > Lambda > UsrCntMgr...initialSetup)
  15. Click "test" for invoke

For client:

  1. update client /src/config.js > apiGateway endpoint
    • Get endpoint: Services > APIs > UsrCntMgr... > stages > ... > Invoke URL: https://{api code}.execute-api.{region}.amazonaws.com/{stage}
    • Put endpoint: Test-request-web service > /src/config.js > apiGateway endpoint > USRCNTMGR: xxxxxx

Inject seed data after deploy

If want to run seeddata immediately after deploying each service, should sequentially deploy services as follows:

  1. MsgCfgMng
  2. ActivitySwitchboard
  3. NotificationMgr
  4. ContactMethodEmail
  5. UsrCntMgr

Alternatively can deploy resource and app for all services and run seeddata for each service in any order.