Custom sleep, pools, agents and Windows template#13
Open
BlWasp wants to merge 1 commit intosynacktiv:mainfrom
Open
Custom sleep, pools, agents and Windows template#13BlWasp wants to merge 1 commit intosynacktiv:mainfrom
BlWasp wants to merge 1 commit intosynacktiv:mainfrom
Conversation
Collaborator
|
Hello, thank you so much for this PR, I'll try to test it when I have some time :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello all!
I recently found myself on an pentest that included Azure DevOps, and I used nord-stream to perform all the extracts I needed.
This PR makes a few improvements that I had to add during testing to adapt to the environment:
--sleep: allows you to specify a custom value for the wait time to retrieve the pipeline output. This is useful in “busy” DevOps environments, where other developers run a lot of pipelines in parallel, causing queues--pool-name: allows you to specify a custom agent pool in case the default “Azure Pipeline” pool is no longer present. This value will be set as the pool name in the pipeline YAML file--default-agent: allows you to specify a default agent pool for deployment. This is not necessarily the same pool as the one specified in the YAML. In the web GUI, this can be found in the pipeline editor -> Triggers -> YAML. ThepipelinesAPI does not allow you to specify this value at creation; you must go through thedefinitionsAPI and specify a “queue” that can be found via thedistributedtask/queuesAPI.--os: useful in cases where all available agents are running Windows. Not only does this require running a PowerShell script instead of Bash, but it also turns out that in Windows, passing variables from a variable group via theenvdoes not work well at all. So I had to trick it by passing the variables directly into the script.I only had Azure DevOps available to perform my tests and modifications. However, I imagine that these types of options could be ported to other CI/CD environments.