Make Mirror Node port configurable

[hendrikebbers]

🆕🐥 First Timers Only

This issue is reserved for people who have never contributed to hedera-enterprise or any open source project in general. We know that creating a pull request (PR) is a major barrier for new contributors. The goal of this issue and all other issues labeled by 'good first issue' is to help you make your first contribution to Hedera.

👾 Description of the issue

Today, we support the installMirrorNode input parameter to start a Mirror Node instance and make it available at localhost:8080. For custom GitHub Runners or Actions, port 8080 may not be used. Therefore, it is important to make the port configurable.

Suggested solution

Provide an additional (optional) input parameter mirroNodePort that defines the port that should be used (default is still 8080). The defined port will than be used to forward the internal Mirror Node port (see kubectl port-forward command). Since the port is now configurable we need to add the used port as an output. Here we suggest to define 2 new outputs:

• mirroNodePort: This output param contains only the port (like 8080).
• mirrorNodeUrl: This output param defines the mirrorNode URL (like http://localhost:8080).

📋 Step by step guide to do a contribution

If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow. A more detailed general documentation of the GitHub PR workflow can be found here.

• [ ] Claim this issue: Comment below that you are interested in working on the issue
• [ ] Wait for assignment: A community member with the given rights will add you as an assignee of the issue
• [ ] Fork the repository: You can do that in GitHub (by simply clicking the 'fork' button).
• [ ] Check out the forked repository
• [ ] Create a feature branch for the issue. We do not have a hard naming definition for branches but it is best practice to prefix the branch name with the issue id.
• [ ] Solve the issue in your branch.
• [ ] Commit your changes: to your branch
• [ ] Start a Pull Request (PR): in the hedera-enterprise repository
• [ ] Check GitHub Actions: Several GitHub Actions will be triggered automatically for each PR. If a GitHub Action fails and you do not understand the cause of that error do not hesitate to add a comment to the PR and ask the community for support.
• [ ] Wait for reviews: Members of the community will review your PR. If a reviewer finds any missing pieces or a problem, he or she will start a discussion with you and describe the next steps for solving the problem.
• [ ] You did it 🎉: We will merge the fix in the develop branch. Thanks for being part of our community as an open-source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a chance to receive cool goodies like a T-Shirt. 🎽

🤔 Additional informantion

If you have any questions, just ask us directly in this issue by adding a comment. You can join the Hedera community chat at Discord. A general manual about open-source contributions can be found here.

[eimontijus]

Hi, I'm interested in this one, please add me as assignee.

[megha-66]

Hi there, can you assign this to me please!

[megha-66]

please checkout the PR. Do I need to start PR in the hedera-enterprise repo?? Pls tell

[hendrikebbers]

no, that is not needed :)

[hendrikebbers]

pr https://github.com/OpenElements/hedera-solo-action/pull/6

[hendrikebbers]

pr is merged. Thank you for the contribution @megha-66