apwide/golive-send-environment-info

Send Environment Information to Golive

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Maintainedlast commit Oct 9, 2025
License
MIT

Pinned Snippet

workflow.ymlSHA-pinned
uses: apwide/golive-send-environment-info@de74eb0362b3848dfc3aad9d884384cd8dd4932e # v1.8.0

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
goliveTokenGolive API Token (Golive Cloud)no
goliveUrlApi Base Url (Golive Server)nohttps://golive.apwide.net/api
goliveUsernameGolive API Username (Golive Server)no
golivePasswordGolive API Username (Golive Server)no
githubTokenGithub token ({{secrets.GITHUB_TOKEN}})yes
targetEnvironmentIdTarget environment the version is deployed tono
targetEnvironmentNameName of the environment in Apwide Goliveno
targetEnvironmentAutoCreateCreate the target environment with provided information if it does not exist yet in Apwide Golive.nofalse
targetApplicationNameType the name of the application to select or create the target environment.no
targetApplicationIdSelect an existing application to use to find/create the target environment.no
targetApplicationAutoCreateCreate the target application with provided name if it does not exist yet in Apwide Golive. N.B. User associated to your connection must have permission to manage applications in order to automatically create new applications. nofalse
targetCategoryNameType the name of the category to find/create the target environment.no
targetCategoryIdSelect an existing category to use to find/create the target environment.no
targetCategoryAutoCreateCreate the target category with provided name if it does not exist yet in Apwide Golive. N.B. User associated to your connection must have permission to manage categories in order to automatically create new categories. nofalse
deploymentVersionNameDeployed version nameno
deploymentBuildNumberBuild number of the deployed version. Ex: $(Build.BuildNumber)no
deploymentDeployedDateDate in ISO-8601 format. Ex: 2023-09-24T12:00:00Zno
deploymentDescriptionDescription of the deployment (markdown is supported). Ex: ✅ **Job** #$(Build.BuildId) - $(Build.DefinitionName) Requested by: $(Build.RequestedFor) Branch: $(Build.SourceBranchName) no
deploymentAttributesDeployment attribute values in key-value JSON format. Ex: { "Requested By" : "me@company.com", "Artefacts" : "https://binaries.company.com/download/232323", "Repository" : "https://github.com/" } no
deploymentIssueKeysComma separated list of Jira issue keys that are deployed. Ex: ECOM-3412,ECOM-6783,PAY-98no
deploymentIssueKeysFromCommitHistoryParse and retrieve the Jira issue keys found in commit history and add them to the current deployment.nofalse
deploymentIssuesFromJqlSet the JQL query used to retrieve and add Jira tickets to the current deployment. Ex: project = ECP AND type in (Story, Bug) AND resolution in (Fixed). More about JQL [here](https://www.atlassian.com/software/jira/guides/jql) no
deploymentAddDoneIssuesOfJiraVersionAdd all "Done" issues fixed in the deployed Jira version to the current deploymentnofalse
deploymentNoFixVersionUpdateDo not add the deployed Jira version to "Fix versions" of the deployed Jira issues.nofalse
deploymentSendJiraNotificationTrigger the standard Jira notification when updating the "Fix versions" of the deployed issues.no
environmentStatusNameType the name of the new status of the environmentno
environmentStatusIdSelect the new status of the environmentno
environmentUrlUpdate the url of the environmentno
environmentAttributesEnvironment attribute values in key-value JSON format. Ex: { "OS" : "Linux", "Location" : "Switzerland", "Owner" : "me@company.com" } no
namedescription
statusStatus of the action