| name | The name of the application to be updated; this string will be used in git branch names so ensure that the provided string is compatible with git's reference naming requirements such as by making sure there are no spaces or periods: https://git-scm.com/docs/git-check-ref-format | yes | — |
| version | The semver version number of the application to be released; this string will be normalized by converting periods to hyphens for use in git branch names but otherwise the user must ensure that the provided string is compatible with git's reference naming requirements | yes | — |
| working_directory_path | The path to where the Iron Bank repo should be cloned | yes | ../tmp_ironbank_workspace |
| ironbank_pat | A GitLab personal access token (PAT) for the specified user who has access to the Iron Bank project - ensure that this is a GitHub repo or org secret so that it is not leaked in the logs: https://docs.gitlab.com/user/profile/personal_access_tokens/#create-a-personal-access-token https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions | yes | — |
| ironbank_username | The GitLab username for the user who has access to the Iron Bank project and whose PAT is being supplied | yes | — |
| ironbank_project_id | The GitLab project id for your Iron Bank project: https://docs.gitlab.com/user/project/working_with_projects/#access-a-project-by-using-the-project-id | yes | — |
| ironbank_project_clone_url | The clone url for your Iron Bank project without the 'https://' in front | yes | — |
| git_commit_author_name | The commit author's name for the update being pushed to Iron Bank | yes | Automated Release |
| git_commit_author_email | The commit author's email for the update being pushed to Iron Bank, e.g., saf@mitre.org | yes | — |
| issue_labels | A comma separated list of labels that will be applied to the issue filed on Iron Bank | yes | Status::Review |
| target_branch | The branch that the merge request will be targetting; if no or an empty input is provided, then the target branch will be the repository's default branch. `development` is usually the default branch on Iron Bank | no | — |
| draft | Whether or not to mark the merge request as a draft; if "true", then the merge request will be marked as a draft - when it is a draft, please ensure that `issue_labels` does not contain "Status::Review" since that forces Iron Bank staff to inspect the issue | no | — |
| update_commands | The bash script that will be evaluated in order to update all appropriate values within the Iron Bank repo; WARNING: only allow trusted content to be placed here, see the security concerns section of the README | yes | — |