[Feature Request] github actions configuration store

There are some information that I would like to store in a central place. It could be URLs, IP addresses, hostnames and other information.
Right now the only way I found to store this centrally is in the Secrets. However the drawback is that you cannot view the information after saving it.
Since information such as IP addresses isn’t necessary that secret it would be beneficial for everyone in the team to be able to view the data to confirm its what they expect it to be, which doesn’t work with Secrets.

Please add a second option “Environment” or “Configuration” similar to Secrets but the information is not hidden after saving. Please make it available in the same way as {{ secrets.NAME }} but probably something like {{ config.NAME }} or similar.

Today similar exists in for example AWS Parameter Store and Kubernetes ConfigMap.

Thanks!

Hi @jbnjohnathan,

Glad to see you in Github Community Forum!

According to the policy, for any feature request, please raise a ticket in below link which is more appropriate.
https://support.github.com/contact/feedback?contact[category]=actions

Since information such as IP addresses isn’t necessary that secret it would be beneficial for everyone in the team to be able to view the data to confirm its what they expect it to be, which doesn’t work with Secrets.

Typically we will set them as environment variable in the workflow, then invoke it with $ in the jobs.
https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#env

on: push
env:          # top level env
  URL: 'https://github.com'
  HOSTNAME: vm2d
jobs:
  job1:
    runs-on: [ubuntu-latest]
    steps:
      - run: echo $URL      # invoke env

And actually we can view the secerts value via workflow, for example, check in artifacts:

      - run: touch test.txt
      - run: |
          echo ${{ secrets.TESTKEY1 }} >> test.txt
      - uses: actions/upload-artifact@v2
        with:
          name: my-artifact
          path: test.txt

Thanks

Hi.

Thanks for the URL to feature requests.
Just to clarify here: While it is indeed possible to use an ENV for the workflow it doesn’t cover multiple ones. Which means you have duplicate information in files which is never good. Imagine a future when someone changes the value in some of the files but not others.
This is why a central configuration store is a a very good idea and I hope it will be implemented soon

1 Like

Hi @jbnjohnathan,

Thanks for your clarification! :grinning:

In the case please raise a feature_request ticket.

no worries, I have done that now : )