actions-marketplace-validations/cloudfoundry-push
Cloud Foundry application manipulation
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit May 11, 2022
- License
- None
Pinned Snippet
uses: actions-marketplace-validations/brickendon_cloudfoundry@bd34d9904e31c9a5efdefaf840783f3e02a33e00 # no releases — HEAD as of 2026-07-10tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| manifest | The path to your CF application manifest | yes | — |
| appname | Application name to use in CF | yes | — |
| appdir | Set this parameter if you want to switch the working dir to push an app | yes | — |
| api | The Cloud Foundry API endpoint | yes | — |
| username | Your Cloud Foundry authentication username (or email address) | yes | — |
| password | Your Cloud Foundry authentication password | yes | — |
| org | The name of the Cloud Foundry organization in which to deploy | yes | — |
| space | The name of the Cloud Foundry space in which to deploy | yes | — |
| domain | The domain name to use in Cloud Foundry | yes | — |
| hostname | The hostname to use in association with Cloud Foundry | yes | — |
| validate | Whether or not to validate the CF API's TLS certificate | no | true |
| debug | Debug your deploy dir to list all folders | no | false |
Outputs
no outputs