93 results found
-
Github app integration
It would be very helpful if you provided an octopus github app in the github marketplace as a way to auth when using github feed/github credentials.
Azure Devops and Terraform cloud currently provide this functionality and it is very helpful as it acts as an organisation service account rather than any 1 individuals account.
Currently if I create a PAT token for octo to use and then I leave the company that puts the other development teams in a bit of trouble, not to mention the security implication of any other user in octo being able to act as me.
…
13 votes -
Fill Promted variables from outer source
Prompted variables are defined manually, the idea is to add the option of filling the values with information of an external source.
For example, fill a Drop Down prompted variable with the values from a column of a MSSQL table.1 vote -
Azure DevOps get CLI Version from Server
We use Azure DevOps and the Use Octopus CLI tool installer. Right now we hard code a version of the Octopus CLI (at Octopus' suggestion) to a known working version. This has caused two issues over the last three months where the CLI version wasn't compatible with the Server. Instead of us guessing at the correct CLI version, the server should suggest one.
The server could respond in multiple ways, e.g.
8.* => Install latest in major version.
7.3.* => Install latest in major and minor version.
8.0.1 => Install exact version.
* => Install whatever is latest.This way…
1 vote -
Octo CLI Support on ARM
I would assume* it's mostly a case of adding
linux-arm64as a runtime argument.Octopus is the /only/ thing that's preventing me from moving my TeamCity agents to Amazon t4g instances. I can accept that the plugin for TC maybe more involved but can we atleast get a build of the cli supporting ARM so that I can manually post manually to Octopus.
7 votes -
Support for library git credentials in GitHub repo feed
Now that we can store git credentials in the library, we would like to use those centrally stored credentials for GitHub Repo feed settings as well.
1 vote -
Support opentelemetry exporters
Both TeamCity and Jenkins have plugins that allow exporting opentelemetry data to any collector service supporting the OTLP protocol. It would be nice if Octopus Deploy also supported this as well, so we could get a full picture of the pipeline, and have metrics on time to deployment from commit to deployment.
2 votes -
bcrypt variable filter
Kubernetes likes to consume hashed values, e.g. for Ingress basic auth we need to provide a secret where the password is already hashed, e.g.: "admin:$apr1$QVF90yb6$JxGT0BWDpw0negAzDy3YT."
This forces us to have two variables: one for the password and the second for its hash
And that may become a problem in the future when we will update one and forget about another
In an ideal world will be so nice to just add something like #{Password | Bcrypt} as a value for a Kubernetes secret
Also, it is a good spot for other algorithms like Md5, Sha-X, ...
1 vote -
Integrate PWA features and Desktop Notifications
It would be nice if we could install our octopus instances as a PWA and integrate desktop notifications for things like deployment events, failures, and possibly manual steps needing approval
1 vote -
TeamCity plugin agentless deployment
When running a deployment and showing its status, specially on longer deployments, the TeamCity agents will be on hold for the duration of the task. On deployments where guided interruption is enabled this is specially taxing on agent licenses.
Since 2020.2.4 TeamCity has introduced agentless builds, where an agent can be detached during the execution of a build, and requires the running process to call TC back via api and inform the build has finished.
This is currently not possible on the plugin and, using powershell, I've found hard to establish the whole deployment status at X point in time.
2 votes -
Upload artifacts via UI
Please add support for uploading artifacts also via the user interface.
Uploading reports/approval documents or other files to a release is currently not possible via an upload button. We have to do a workaround using a script that uploads files from a specific folder or using the API to attach files to a release.
Especially during Octopus approval steps people need to upload documents.
14 votes -
Add support for Keyfactor (Security and SSL) Certificate management
We use keyfactor (https://www.keyfactor.com/platform/certificate-lifecycle-automation/) for Certificate lifecycle Automation. It would be great if Octopus could integrate with this keyfactor to allow for issuance, renewal, inventory, import and storage of new certificates.
1 vote -
Support environment variables for all `octo` CLI commands / flags
I posted about this as a GitHub issue as well (https://github.com/OctopusDeploy/OctopusCLI/issues/142). Basically, it would be nice if the
octoCLI could read environment variables for all of its commands and flags. This would make CI easier since values could be easily changed and tested without having to make code changes.Thank you!
1 vote -
Allow setting Build Information WorkItems
Currently Push Build Information API and command line ignores values set on WorkItems field, only to auto populate with values once one of the Integration extension is enabled.
Please allow Push Build Information API and Command line to
- Set WorkItems with values set on request
- Do not override values even if Issue Tracker extension is enabled5 votes -
Subscriptions - Multiple Headers
It would be great to add multiple headers in octopus subscription payload requests. Atm, it looks to be limited to just one.
Thanks to this, it would be possible to better control the logic through the application that rewrites/parse the payload and send to a specific webhook
2 votes -
Add link/URI within the Octopus, deployment output to support one-click access from CI/CD tools
If you use an Octopus, build/pipeline task within Azure DevOps Server/Services (or another CI/CD tool) to trigger a deployment, it would be useful to have a URI within the feedback output by the deployment within the Azure DevOps (or other CI/CD tool) build/pipeline.
This would allow the Octopus deployment to be accessed via a single click of that URI (as opposed to having to navigate back into Octopus and find the project, the release and then the deployment).
1 vote -
Integration with Azure App Configuration
Please provide integration with Azure App Configuration. We need the task to download variables in the process runtime. This will allow to use Azure CMDB and Octopus for deployments.
10 votes -
codebuild
Add an official Octopus plugin for AWS CodeBuild to integrate with Jira.
https://octopus.com/docs/managing-releases/issue-tracking/jira#availability
5 votes -
Let users select apps to deploy for a Jira issue
Currently our workflow for indicating/knowing what app/s need to be deployed for a Jira issue or a Jira release (of multiple issues) is to manually enter/bundle up these from the Jira issue descriptions which we fill out.
What would be amazing though would be if the Octopus Jira integration plugin rendered a smart "section" into the Jira issue, where you could (1) select which apps need to be deployed (from Octopus), and (2) then get a read-only envs+releases matrix like in the octo dashboard so people can see where it's deployed currently.
Furthermore, on the Jira release/deployment page (assuming this…
1 vote -
JSON Template for Subscriptions
Allow the json payload used when setting up Subscriptions to be templated in the same way as config.
If you could specify the json with embedded octopus variables you could integrate with many many other tools without the need to add a custom step at the end of each deployment. (eg. MS teams)2 votes -
Add support for SVN (subversion) VCS commit information
After pushing build information from a TeamCity project that was building some code from SVN (subversion) version control system, I noticed that while the package in octopus did have the commit section filled out as expected, the commits were NOT there when creating a release with that package. This meant that we couldn't automatically generate the release notes based on commit messages. I contacted octopus support and we eventually figured out that SVN is not supported.
3 votes