nextflow-io / nextflow-io/nextflow
Please add parameter to select IP address provisioning type when autoPoolMode and vnet is set in config file
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
New feature
Hi, it would be good to have an option to select IP address provisioning type (BatchManaged/UserManaged/NoPublicIPAddresses) when the autoPoolMode is set to true and a pool has a vnet assigned.
Usage scenario
As a data engineer
I would like to be able to run a pipeline on an automatically created pool in azure batch
that is assigned to specific vnet and has a IP address provisioning type set to one of the options: BatchManaged/UserManaged/NoPublicIPAddresses
so that we're meeting company compliance policies.
Suggest implementation
Example config for azure batch with new parameter:
azure {
managedIdentity {
system = true
}
storage {
accountName = "storageaccount"
}
batch {
accountName = 'batchaccount'
location = 'westeurope'
autoPoolMode = true
pools {
auto {
virtualNetwork = 'vnet'
ipAddress = 'BatchManaged/UserManaged/NoPublicIPAddresses' #works only if vnet is defined
}
}
}
}
within that setup the azure batch pool will be created with an expected IP address provisioning setup.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Azure Batch configuration for autoPoolMode, virtualNetwork, and pool creation. Check how the proposed ipAddress values map to Azure Batch's IP address provisioning options when a VNet is assigned. Done means the configuration accepts the selected value and creates the automatic pool with the requested provisioning type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, groovy
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100