uipath-mock-slack

periodic-uipath-mock-slack

• Periodic-uipath-mock-slack

Build and update workflows

Every developer must perform build after making required changes as they wish. The build toll make sure that the element repository is in sync with the template structure and verifies for any changes in Github Actions CI/CD updates. After running this, you might see some diff in your repo regarding the GHA workflows and other possible template updates. So, just verify the changes and commit them to your PR branch.

To build and update GHA workflows:

    ./scripts/build --template

Note: Occasionally, you may need ./scripts/build --template to include any changes from template repository

TIP: You can run ./scripts/verify to verify whether you need to build

Test

PreReqs - done once for all node npm projects

1. install nvm brew install nvm
2. install node 14 nvm install 14 --lts

• if already installed use node 14 nvm use 14

3. install dependencies npm install
4. include ~/.npmrc to the following

•   //registry.npmjs.org/:_authToken=YOUR_NPM_REGISTRY_TOKEN
    //npm.pkg.github.com/:_authToken=YOUR_GITHUB_TOKEN
    @cloud-elements:registry=https://npm.pkg.github.com/cloud-elements

unit tests

    npm test

You can test the element template structure valid or not using test tool. If you are required to rebuild the element it will alert you as such. And just follow the instructions. The same test will be performed in the pre-merge GHA workflow.

   ./scripts/verify

Periodic Template

This repo was created using cloud-elements/peridic-template which is a modified version of our service template noted below.

Service Template

The base template was created using cloud-elements/service-template. Refer to TEMPLATE.md or service-template/TEMPLATE.md for additional information.

Deploy

You can use cargo tool to deploy. First install cargo using brew install cargo if you don't have it installed. Then trigger the deploy using below command

    cargo make deploy-trigger -- --env {ENVIRONMENT} --interactive

Note: You can skip --interactive, that uses latest tag to deploy the element. If you use interactive mode, you can choose which version to deploy

Dry run

This helps to verify/debug what will be deployed, but no real deployment will be triggered.

    cargo make deploy-trigger -- --env {ENVIRONMENT} --interactive --noop

Note: Use cargo make deploy-trigger -- -h to find help

Environments

• snap0

• es-uswest-alpha-0

• es-euwest-stage-0

• es_eunorth_prod_0

• es-jpeast-prod-0

• es-useast-prod-0

  Note: More will be added soon