Forem: rdlucas2

Bob Ross blesses your Repo With Happy Little Accidents

rdlucas2 — Fri, 18 Sep 2020 04:25:12 +0000

My Workflow

The action is named "happy-little-action". This workflow is for anyone who wants to feel the joy of painting in their repository. Bob Ross's gentle spirit will add a happy little accident (a text file containing some of his words of wisdom or a PNG of one of his paintings) to your repository after each commit or pull request.

Submission Category:

Wacky Wildcards

Yaml File or Link to Code

rdlucas2 / happy-little-action

Happy little accidents appear in your github repository

happy-little-action

Happy little accidents appear in your github repository

Inputs

`github-token`

Required Your Github Token used to auth to github rest api, set to: "${{ secrets.GITHUB_TOKEN }}".

Example usage

uses: rdlucas2/happy-little-action@v0.0.13
    with:
        github-token: ${{ secrets.GITHUB_TOKEN }}

View on GitHub

**Example Yaml Workflow File**

Additional Resources / Info

This is the last of my entries to the actionsHackathon submissions! I found some of the resources from existing github repositories, that saved me a lot of time not having to gather the quotes and images. I learned a little using octokit for the first time which was nice too. Thanks for sticking around and happy coding!

Link to where I found the Quotes

Link to where I found the Paintings

My other actionsHackathon submissions:

Let me google that issue for you

Tell Alexa to Trigger Your Deployment

Alexa Notifies You When Someone Stars Your Repository

Let me google that (issue) for you

rdlucas2 — Mon, 14 Sep 2020 05:02:52 +0000

My Workflow

This is the "lmgtfy-action"... on issue creation, the action will trigger and automatically take the issue creator's issue title or body content and use it to create a let me google that for you short url as a reply to the issue. This is just a wacky wildcard, as it's bad open source etiquette to snarkily reply to users with a let me google that for you link! Hopefully it will be unlikely that you're getting poor quality comments that the answer can be googled for as well. This might have been better as a Rick Roll even, as a search on the issue will likely turn up irrelevant results in most cases. I was mostly using this as a learning opportunity to experiment with JavaScript github actions!

This isn't being used by anything yet, it was solely created as an actionsHackathon submission.

Submission Category:

Wacky Wildcards

Yaml File or Link to Code

**Yaml workflow file**

rdlucas2 / lmgtfy-action

Let me google that for you action

Add this action to your repository to auto reply to issues with a let me google that for you link.

Inputs

`github-token`

Required Your Github Token used to auth to github rest api, set to: "${{ secrets.GITHUB_TOKEN }}".

`field-to-query`

Required Use the title or body of the issue to search for. Default: "title"

Example usage

uses: rdlucas2/lmgtfy-action@v0.0.7
    with:
        github-token: ${{ secrets.GITHUB_TOKEN }}
        field-to-query: 'body'

View on GitHub

Additional Resources / Info

Nothing too special about this one. I used chrome dev tools to inspect the network tab while on the "let me google that for you" site when I clicked the button to produce the short url. I copied the relevant info to postman to play with the call, then went about learning how to setup the JavaScript action. Once I did a test run to see what the payload returned, it was pretty easy to plug in the relevant info to make the necessary REST calls to the lmgtfy API and the GitHub API to create a response to the issue. I learned about a tool that was new to me... ncc, which was a nice find that I may use in future projects.

Thanks for sticking around and happy coding!

Register Azure IoT Edge Device on Existing Hub

rdlucas2 — Mon, 07 Sep 2020 20:00:04 +0000

My Workflow

This workflow is designed to register a new Azure IoT Edge Device on an existing Azure IoT Hub. I made my own custom docker action to handle setting up the azure cli, and read from a file in your repository which is a list of device names you'd like registered on your hub. Once the devices are registered on the hub, you can get their connection strings, and use the hub to deploy code to them as well. See the additional info section for more on that later in this article.

This isn't being used by anything yet, it is just a proof of concept for the actionsHackathon submission.

on: [workflow_dispatch]

jobs:
  register_iot_job:
    runs-on: ubuntu-latest
    name: A job to register an IoT Edge Device on Azure IoT Hub
    steps:
    - name: Checkout
      uses: actions/checkout@v2
    - name: Register step
      id: register
      uses: rdlucas2/actionsHackathonSubmissions@v0.0.9
      with:
        azure-sp-client-id: '${{ secrets.AZ_SP_CLIENTID }}'
        azure-sp-password: '${{ secrets.AZ_SP_PASSWORD }}'
        azure-tenant-id: '${{ secrets.AZ_TENANT }}'
        azure-iot-hub-name: '${{ secrets.AZ_IOT_HUB_NAME }}'
        device-list-file-path: '/github/workspace/devices/list.txt'

I added secrets for my azure account information, although it wasn't necessary for some of them to be secret. The last item on the list, "device-list-file-path", is just a text file with each line containing the name of a device you'd like registered on the hub - which is why the checkout step is necessary. It is important to note that when you use a docker action, it will automatically pull in /github/workspace as a volume in the container.

On a successful run the devices should appear in your IoT Hub. Note that if a device was already registered, it will show an error message, but it should continue to register other devices and won't overwrite any existing.

Submission Category:

Interesting IoT

Yaml File or Link to Code

**Yaml file**

rdlucas2 / actionsHackathonSubmissions

playing around with actions

Register Azure IoT Edge Device

This action Registers a new IoT Edge Device on a given Azure IoT Hub.

Inputs

`azure-sp-client-id`

Required Azure Service Principal Client ID.

`azure-sp-password`

Required Azure Service Principal Password.

`azure-tenant-id`

Required Azure Tenant ID.

`azure-iot-hub-name`

Required Azure IoT Hub Name.

`device-list-file-path`

Required Device List File Path.

Outputs

None

Example usage

uses: rdlucas2/actionsHackathonSubmissions@v0.0.1

with: azure-sp-client-id: '${{ secrets.AZ_SP_CLIENTID }}' azure-sp-password: '${{ secrets.AZ_SP_PASSWORD }}' azure-tenant-id: '${{ secrets.AZ_TENANT }}' azure-iot-hub-name: 'MyExistingHubName' device-list-file-path: '/devices/list.txt'

View on GitHub

**Yaml file**
For this one, I created my own custom action, but then used the checkout action and my custom action in concert to read device names from a file in the repo, and register them on the Azure IoT Hub. I did not register this action on the marketplace yet, but have created some pre-release candidates of it. I'd move it into it's own repository instead of utilizing my actions hackathon repo.

Additional Resources / Info

Used the tutorial here for some of the setup: IoT Edge Linux Quickstart.

If you examine the code I wrote, you'll see I followed the IoT Edge Device tutorial linked above, and used ARM to deploy an azure vm with the IoT runtime on it, using the newly registered device's connection string to it. I then went into the portal and deployed the "simulated temperature sensor" marketplace code to this device through the portal page on the hub. I think this workflow could be built out to manage devices on an azure IoT hub. In addition to adding new devices, you could build out actions like deleting devices, deploying code to devices, and perhaps even collecting telemetry from devices. This was mostly a learning opportunity for myself. I had made a few other entries utilizing actions created by other individuals, and this one I wanted to explore custom docker actions.

I'm determining the proper workflow for this, as it might make sense to combine this in some way with a deployment action, where when you connect a new device, it can reach out to a repository to register itself on the hub, then update the hub connection string, deploy some code to the device with that updated connection string, then go about collecting telemetry from the device. I certainly learned a lot about how actions behave from this experience. Here are some links to my other submissions:

Tell Alexa to trigger your deployment

Alexa notifies you when someone stars your repository

Tell Alexa to trigger your deployment

rdlucas2 — Wed, 19 Aug 2020 03:10:27 +0000

Ryan

@rdlucas2

Alexa, trigger my deployment. My second submission to the #actionsHackathon for @ThePracticalDev. Run your @github action with @alexa99 voice command.

03:05 AM - 19 Aug 2020

My Workflow

The "on voice" workflow uses the workflow_dispatch event to trigger the github action via the github rest api. This action is just a proof of concept for allowing you to interact with your repo by voice, and is not used anywhere except the repo I've created for this actionsHackathon submissions.

Submission Category:

Interesting IoT

Yaml File or Link to Code

onvoice.yml

Additional Resources / Info

The code used in the action is really nothing special. I've left it as the "default" action template but just changed the event trigger to "workflow_dispatch". This allows me to call the rest api targeted at the "onvoice.yml" file, which in turn would kick off any deployment defined within. The idea here is that you could tell alexa to trigger {your project name} deployment, and have it kickoff this process.

To set this up, you'll need an IFTTT account, and add the Alexa service.

Once you connect the Alexa service, setup a new trigger for "say a specific phrase".

Fill out the form with something like "my deployment" - when you interact with alexa you'll say "Alexa, trigger my deployment"

Then, for the action - search for "webhook" and set the action as "make a web request"

This is where things got a little funky. I could not get this web request action to properly authenticate to the github rest api. I tried doing basic auth in the url with https://user:pat@api.github.com... which works with curl but not via ifttt. Unfortunately the ifttt interface doesn't give you a lot of options for customizing your http request, so I ended up setting up an azure function to bypass this problem. My webhook instead calls the function app URL, which in turn calls the workflow dispatch. The curl for the call looks like this:

curl \
  -X POST \
  -H "Accept: application/vnd.github.v3+json" \
  https://api.github.com/repos/{USER}/{REPOSITORY}/actions/workflows/{WORKFLOW_ID_OR_YML_FILE_NAME}/dispatches \
  -d '{"ref":"{BRANCH_NAME}"}' \
  -u {USER}:{PAT}

Anything surrounded with curly braces {} would be specific to your account/repository. Learn how to make a Personal Access Token (PAT) here: Create a PAT. You can read up on the workflow_dispatch event here: Workflow Dispatch Trigger Event and the github rest api for calling the workflow dispatch event here: Workflow Dispatch Rest Api Call.

Alexa notifies you when someone stars your repository

rdlucas2 — Sat, 15 Aug 2020 03:32:30 +0000

Ryan

@rdlucas2

@ThePracticalDev #actionshackathon my submission, get a notification on your Alexa when someone stars your repo. dev.to/rdlucas2/alexa…

03:55 AM - 15 Aug 2020

My Workflow

The workflow is a silly one, for vain individuals who want to know when people are starring their code on github! This isn't a published marketplace action, just something spun up in a workflow, so there's no official name... I'll just go with the name of: On Repository Starred - get a notification on your Alexa device(s). This isn't being used anywhere except for the repository I created for submissions to this hackathon.

Submission Category:

Interesting IoT

Yaml File or Link to Code

Action YAML file

Additional Resources / Info

All this required was an http request, so used an existing action to accomplish this. On the Alexa side, what's required is adding the skill Notify Me. With the skill added, all you have to do is say "Alexa, open notify me" - and the app will send you an email with the secret required to get this running. Add the secret to your github secrets, and craft a custom message in the json body to get your notification. The message I've made in the code says who starred which repository (yes, you could add this to multipe repos). Your Alexa device will only make a sound when a notification is received, you have to ask to read or hear your notifications to actually listen to the response.

This is kind of a silly example - if your repository becomes popular and you're getting a lot of stars you probably don't want to hear that many notifications! Others have already made an IFTTT action, which could be used to kickoff processes for any of your other smart devices with relatively little hassle... think, you could flash your hue lights red when an issue is created, or maybe play the final fantasy victory song when a milestone gets completed.

Happy coding :-)