Replies: 100 comments 28 replies
-
That's a neat idea that I hadn't considered. We'll put this on the backlog. Thanks for the feedback, @Suchit8. |
Beta Was this translation helpful? Give feedback.
-
Is there a feature request for this? |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
Hello, |
Beta Was this translation helpful? Give feedback.
-
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 ? |
Beta Was this translation helpful? Give feedback.
-
Is there any update on the feature request? As a result, workflow dispatch will be a much more powerful tool |
Beta Was this translation helpful? Give feedback.
-
This feature would be super useful for me as well! |
Beta Was this translation helpful? Give feedback.
-
+1 (missing this feature, is the only feature I miss after migrate from Jenkins to Github action, will be nice to be added) |
Beta Was this translation helpful? Give feedback.
-
Is there any update on this? |
Beta Was this translation helpful? Give feedback.
-
Voting too, we need it as well. |
Beta Was this translation helpful? Give feedback.
-
+1 Would be a great feature to have |
Beta Was this translation helpful? Give feedback.
-
Hi is there any update regarding the same ? because if we can populate the value dynamically it will make GitHub action more usable for conditional base deployment as well as for other use case scenarios |
Beta Was this translation helpful? Give feedback.
-
+1, please make it happen. |
Beta Was this translation helpful? Give feedback.
-
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] }}
Beta Was this translation helpful? Give feedback.
All reactions