Home

Ansible Azure module development

Notification from Ansible/ansible

Development tips for ansible

Document syntax

These formatting functions are U() for URLs, I() for option names, C() for files and option values and M() for module names. Module names should be specified as M(module) to create a link to the online documentation for that module.
Keep the return value as simple as we can in create/update module, because the listed reason.

The module should have an _instance_to_dict function, to flatten the instance to dict. It should keep the simplest information. The fact-module return value should show details, using as_dict() from SDK.

Sync from the Ansible/ansible repo

It now uses Travis-CI to run a auto sync job every day to sync changes from Ansible/ansible repos' devel branch to this devel branch.

If you cannot wait for the next auto-sync, go to the Travis CI's VSChina/ansible travis branch, click the restart build.

If there is something unexpected happen, make our devel branch is conflict with Ansible/ansible devel branch, and cannot sync from it.

Click our repo's Settings, temporarily close the protected of devel branch
Go to the Travis CI's VSChina/ansible for-push branch, click the restart build
Don't forget to open the protect for devel branch again

Auto run integration test for all azure modules

It uses Travis CI to run all the ansible azure module's integration test in one build every week. The purpose is to see whether there is a breaking change from the Azure Rest API. To run the integration test, it uses "Java Tooling Tests with TTL = 2 Days" subscription.

Because of the time limit of CI platform, it runs integration tests in several jobs in the one build. Each job has an id to identify which sequence of test in the test list should run. At the very beginning, it contains 3 jobs, and each job runs 8 integration test. If the number of integration test is increase out of range, add another id in matrix

Provide feedback

Saved searches