According to the examples in the documentation:
env:
OCTOPUS_URL: ${{ secrets.OCTOPUS_URL }} # address of Octopus Deploy instance (i.e. https://demo.octopus.app)
OCTOPUS_API_KEY: ${{ secrets.OCTOPUS_API_KEY }} # API key used with Octopus Deploy instance
OCTOPUS_SPACE: '<spacename>' # or you can specify a Space ID
steps:
- uses: actions/checkout@v2
- name: Push build information to Octopus Deploy 🐙
uses: OctopusDeploy/push-build-information-action@v3
with:
packages: |
<packageId1>
version: '<versionofpackages>'
The OCTOPUS_SPACE parameter can support a Space ID instead of just a name. In practice, however, this raises an error due to being unable to find a space with the name Spaces-22.
The majority of other octopus CLI commands allow Space ID or name to be used interchangeably; we have a strong preference to use IDs in our workflows instead of names which may be changed. Is it possible to add support for Space IDs to this action to be consistent with the CLI?
According to the examples in the documentation:
The
OCTOPUS_SPACEparameter can support a Space ID instead of just a name. In practice, however, this raises an error due to being unable to find a space with the nameSpaces-22.The majority of other octopus CLI commands allow Space ID or name to be used interchangeably; we have a strong preference to use IDs in our workflows instead of names which may be changed. Is it possible to add support for Space IDs to this action to be consistent with the CLI?