Github workflow_dispatch input dynamic values

[Suchit8]

Can we have a feature in the GitHub actions to populate the workflow_dispatch input values dynamically, maybe using some API response or using other GitHub workflow outputs?

Ex: Current workflow
on:
workflow_dispatch:
inputs:
SOURCE_REGION:
type: choice
default:
required: true
options:
- us-west-1
- us-west-2
- us-east-1
- eu-west-1

Ex: Feature looking for-
on:
workflow_dispatch:
inputs:
SOURCE_REGION:
type: choice
default: [ SOME FALLBACK INPUT ]
required: true
options:
- {{ API_RESPONSE[0] }}
- {{ API_RESPONSE[1] }}
- {{ API_RESPONSE[2] }}
- {{ API_RESPONSE[3] }}

[ethomson]

That's a neat idea that I hadn't considered. We'll put this on the backlog. Thanks for the feedback, @Suchit8.

[niralkk]

@ethomson, any update?

[franjofranjic27]

still in the backlog?

[ivandres73]

+1

[Michael-Dawson-Sage]

Please

[Cozgg]

+1

[allcloud-sahar-hagbi]

Is there a feature request for this?

[pkernevez]

Is there a feature request for this ? (too)

[rgoodwin]

This (or something like it) is really important to support dynamic environments. It's getting pretty common to spin up environments for a single branch or testing of a release. Esp with microservices it can become a lot of work to update N number of workflow dispatch input choices.

While it could be environment variables that would be limiting and in a way bring one back to the same issue. Having to update data somewhere. One thing that might help a lot of users is to support a dynamic environment field in the workflow_dispatch that was dynamically generated from environments declared at the repo level.

[cschleiden]

👋

One thing that might help a lot of users is to support a dynamic environment field in the workflow_dispatch that was dynamically generated from environments declared at the repo level.

Have you seen the type: environment input field - https://github.blog/changelog/2021-11-10-github-actions-input-types-for-manual-workflows/?

[Nokel81]

It also would be very useful to be able to fill out the options of the dropdown based on the tags of some other repository.

[tuhin-sheikh-cmc]

I was looking for something like this too so that we can trigger deployment from the latest tags created.

[amazingandyyy]

this feature is very needed, in our use case, we just want to have a list of option which is the file name listed from the root, for example make the output of ls -l to be input options for a GHA run

[kuczko]

Hello,
I would say we should have release version as one of dynamic choice input types. That way we can have a button for release deployment and we can select release number from drop-down list.

[AmitKatyal-Sophos]

I've a slightly different use-case. Any thoughts on handling the same ?

on:
workflow_dispatch:
inputs:
deployment_env:
type: choice
default:
required: true
options:

• dev
• qa
• prod

deployment_region:
type: choice
default:
required: true
options:
${Region}

Here, ${Region} list should be populated based on the dev/qa and prod env.

[guenoledc]

In the meantime, has anyone tried to update the workflow file (its a yaml after all) from another event, committing it to the repo, so when end-user want to use the workflow_dispatch the values are in there.

I know it is a bit arsh design but would it work ?

[Nokel81]

No. What I ended up doing was using the repository_dispatch event (making sure that I used a child field because GitHub also thought it was a GREAT idea to limit the number of to level field in the payload of that event) and just writing a custom CLI.

[guenoledc]

I see, So to execute the workflow you do not use the github UI, right ?

If so obviously it is simpler to control.

What about a github pages app so it all stays in github ?

[Nokel81]

I don't know about that. This was just work around that found.

[shaypi]

Is there any update on the feature request?

As a result, workflow dispatch will be a much more powerful tool

[camilla-storytel]

This feature would be super useful for me as well!

[bvtk]

+1

[dil-kpogany]

+1

[twskipper]

+1

[jawnclarke]

+1

[MahmoudMabrok]

+1 (missing this feature, is the only feature I miss after migrate from Jenkins to Github action, will be nice to be added)

[fede843]

+1

[Doenerpapst]

+1

[danljfrog]

+1

[JD10NN3]

+1

[skoval67]

+1

[ns-mkusper]

+1

[Erica-West]

+1

[pawel-wiszniewski]

+1

[IsaacJames]

+1

[NihinFaj]

+1

[jhflemos]

+1

[scottmcburney]

this would help me SO MUCH IF IT EXISTED.
I would love a "choice" input to a workflow that can cull the options from some source.

[zatarain]

This feature is really needed to avoid user input errors or typos.

Is there at least a recommended workaround? 🤔

[adolsalamanca]

Is this at least being considered for the near future?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[jmichalicek]

I was just looking into this sort of functionality myself so that I could update our production release workflow. We have an action which only triggers from workflow_dispatch and requires a docker image tag (right now it forces the rest) for the image to deploy. I'd love to have a way to populate it from a list of images which have been deployed to staging or even be a text input (as it is now) which is pre-filled with the most recent image deployed to staging.

The latter I could more or less accomplish by just having two inputs, the image tag and a "promote_current_staging" boolean and if the "promote" option is selected, check what is there (or have staging deployments record it somewhere), otherwise use the hand-typed input.