Transfering OpenElements/hedera-solo-action to Hiero

[hendrikebbers]

This proposal is to transfer the project OpenElements/hedera-solo-action to Hiero.

Current project location: https://github.com/OpenElements/hedera-solo-action

Suggested name under Hiero: solo-action

Supporters of the project

• Jeromy Cannon (Hashgraph)
• George Spasov (LimeChain)
• Alex Popowycz (Hedera)

Project description

The project defines a GitHub Action for setting up a Solo network. An overview of the usage and idea of the action can be found in this article.

The GitHub action can easily be integrated with any project to run tests in CI/CD against a solo network by using GitHub Actions. The Action provides information about the network and a dedicated account as environment variables.
A minimalistic use case of the action that only prints the account information looks like this:

- name: Setup Hedera Solo
  uses: OpenElements/[email protected]
  id: solo
  
- name: Use Hedera Solo
  run: |
    echo "Account ID: ${{ steps.solo.outputs.accountId }}"
    echo "Private Key: ${{ steps.solo.outputs.privateKey }}"
    echo "Public Key: ${{ steps.solo.outputs.publicKey }}"

The Action can be configured as some parameters today as defined in the README. Additional parameters can be easily added in future versions.

State of the project

The project is still released under 0.X but is stable and ready for productive use. The action has already several releases and can be found at the GitHub marketplace. The project is developed by hendrikebbers but some people solved 'good first issues' during hacktoberfest 2024.

Usage of the project

The GitHub Action is currently used in the hedera-enterprise project and executes over 350 integration and unit tests for each PR / commit. An example can be found here.

Vision of the project

The GitHub Action can be used for the development of all our SDKs and the TSK for the SDKs. Next to that application and library developers can use the action to execute automatic tests not against testnet anymore. Having 1 standardized GitHub Action for those use cases will be a huge benefit.

[Perseverance]

This proposal makes complete sense. It belongs under the Hiero umbrella and will be super useful for many automated quality assurance efforts. I support it!

[popowycz]

Definitely a +1 from me.

Not a blocking questions - Is this expected to remain independent of Solo or be merged in when Solo is migrated into Hiero?

[hendrikebbers]

@popowycz
I suggest to have it separated. Having it on the GitHub marketplace needs a specific repository layout. See https://github.com/marketplace/actions/hedera-solo