reload/Platform.sh Deploy status
Detect if a platform.sh site has deployed successfully
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| PLATFORMSH_KEY | API key for connecting to Platform.sh | yes | — |
| PLATFORMSH_ID | ID for the Platform.sh project. | yes | — |
| ENVIRONMENT_NAME | Which environment to check against - defaults to pr-NUMBER | no | pr-${{ github.event.pull_request.number }} |
| ACTIVITY_TYPES | Comma-seperated types of deployments to wait for. Default: push - See types here: https://docs.platform.sh/integrations/activity/reference.html#environment-activity-types | no | push |
| DEPLOY_STATUS_PATH | The location of the deploy-status file on the website. | no | /sites/default/files/deploy-status |
| PSH_DETECTION_WAIT | How long should we maximum wait for PSH to detect the push? If the branch doesnt exist in the PlatformSH GIT Remote, this is how long the action will take. Actually inactive environments get detected instantly. Default: 30 seconds. | no | 30 |
| ALLOW_CANCEL_CRON | Can we cancel on-going crons, to speed up deployment? default: 0 | no | 0 |
Outputs
| name | description |
|---|---|
| url | The ready-to-connect URL |
| state | The state of the deployment, parseable by GitHub Deployment Status |
| state_description | Short description of the state, such as error message. |