Skip to content

Managed CCF proposal voting

Actions
Automated voting for applications in CCF
v0.2.2-alpha
LatestPre-release
Star (0)

Action for proposal voting in CCF

This GitHub action is designed to automate voting for proposals in a CCF network.


Pre-reqs

These action require 2 secrets to be stored in GitHub.

  • MEMBERCERT - The certificate that has access to the network, which will be used to sign the transactions for CCF.

  • MEMBERKEY - The private key associated with the MEMBERCERT.


Example workflow: Sample

on: [push]

jobs:
  ccf-deploy:
    runs-on: ubuntu-latest
    name: Deploy a CCF application and accept it
    env:
      CCF_URL: '<your ccf endpoint>/'
    steps:
      - name: Checkout
        uses: actions/checkout@v3
      - name: CCF deploy
        uses: msftsettiy/[email protected]
        id: deploy
        env:
          CERTD: ${{ secrets.MEMBERCERT }}
          KEYD: ${{ secrets.MEMBERKEY }}
        with:
          application: '<path to your bundled application>'
      - name: Get the proposal id
        run: echo "The proposal id is ${{ steps.deploy.outputs.proposal }}"
      - name: CCF approve action
        uses: msftsettiy/[email protected]
        id: vote
        env:
          CERTD: ${{ secrets.MEMBERCERT }}
          KEYD: ${{ secrets.MEMBERKEY }}
        with:
          proposal: ${{ steps.deploy.outputs.proposal }}
      - name: Get the status
        run: echo "The proposal id is ${{ steps.vote.outputs.status }}"

Managed CCF proposal voting is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

About

Automated voting for applications in CCF
v0.2.2-alpha
LatestPre-release

Managed CCF proposal voting is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.