Package: azureips
Azure Vacant IPsThis package gives you the list of private ip address that are not allocated to any resource. This helps in below scenario.
If you want to make an ip static in azure you need to specify the IPs, this means you have to manage the IPs by yourself. This package helps you by
getting you the list of IPs that are not allocated and this saves you from cumbersome process of keeping track of IP addresses allowed.Creating Network interfaces with dynamic ip is easy but for static ip address you need the ip that is not allocated.Usage and how it works.Installationpip install azureipsYou can import it to use it with your python program.Importing in python applicationfrom azureips.vacant_ips import VacantIP
vacant_ips = VacantIP(client_id, client_secret, subscription_id, tenant_id,
                 token_url, base_url, api_version, subnet, vnet, resource_group, count)
vacant_ips.get_vacant_ips()
#base_url, api_version and token_url can be empty strings.This will return an array of ipsOptionsclient_id: Client id of the app generated in service principleclient_secret: Client Secret obtained from appsubscription_idtenant_idtoken_url: Not requiredbase_url: Not requiredapi_version: Not requiredsubnet: Subnet to search for unallocated IPvnet: Vnet to which the subnet belongsresource_group: Resource group in which vnet is presentcount: Number of IPs that you want as outputContributingWhen contributing to this repository, please first discuss the change you wish to make via issue, or any other method with the owners of this repository before making a change.Please note we have a code of conduct, please follow it in all your interactions with the project.Pull Request ProcessEnsure any install or build dependencies are removed before the end of the layer when doing a
build.Update the README.md with details of changes to the interface, this includes new environment
variables, exposed ports, useful file locations and container parameters.You may merge the Pull Request in once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer to merge it for you.Code of ConductOur PledgeIn the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, or sexual identity and
orientation.Our StandardsExamples of behavior that contributes to creating a positive environment
include:Using welcoming and inclusive languageBeing respectful of differing viewpoints and experiencesGracefully accepting constructive criticismFocusing on what is best for the communityShowing empathy towards other community membersExamples of unacceptable behavior by participants include:The use of sexualized language or imagery and unwelcome sexual attention or
advancesTrolling, insulting/derogatory comments, and personal or political attacksPublic or private harassmentPublishing others' private information, such as a physical or electronic
address, without explicit permissionOther conduct which could reasonably be considered inappropriate in a
professional settingOur ResponsibilitiesProject maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.