Deploy/Publish package using PowerShell or REST API.
- Dominant language
- No language data
- Stars
- 346
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
Not exactly related directly to a problem, but the current deployment option isn't the best for us.
**Describe the solution you'd like**
Any way to deploy static contents besides using the Task? For example, using an API to post the zip (package) or by using a PowerShell script? We have on-premise build servers running Windows and we'd like to use that to deploy our packages - however, we are currently limited to use an ubuntu server (have only tested hosted ones at the moment).
**Additional context**
The reason we require this is, we need to, depending on the stage, configure a static file (json) on the build directory and we have lot's of logic implemented in PowerShell. Each stage has, similar variables, however, their values are different.
**Describe alternatives you've considered**
An option is to port our code in bash, or something else (python?) - however, this would be a little complicated and time consuming.
I have found another issue #306 where the user requested if the source was available - however, it seems not.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.