How to pass ENVIRONMENT VARIABLES to ansible-test integration --docker

sumanth-lingappa · January 3, 2024, 6:17pm

How to pass ENVIRONMENT VARIABLES to ansible-test integration --docker.

I am writing integration tests for netscaler.adc collection.

This collection is a collection of modules to configure the NetScaler ADC via API (each ansible module invokes NetScaler NITRO APIs)

The collection takes API authentication via each task or via environment variables (github link below)

How can I send my environment variables to ansible-test integration --docker ?

I have seen integration_config.yml. It works but there is no way I can send my credentials securely.

ENV VARS would be best in my case.

Please help.

github.com

netscaler/ansible-collection-netscaleradc/blob/438a2e50bed62e832a397ee0747c7a0901cab091/playbook_anatomy.md?plain=1#L18


      
          
          gather_facts: false # Since the module runs on localhost, we don't need to gather facts
          
          tasks:
            - name: Name of the task
              delegate_to: localhost # Since the module runs on localhost, we need to delegate the task to localhost
              netscaler.adc.service: # Name of the module. We recommend to use the fully qualified name of the module
                # The following are the NITRO authentication parameters. Refer to the module documentation for the list of supported parameters.
                nsip: 10.0.0.1 # This can also be given via NETSCALER_NSIP environment variable
                nitro_user: nitrouser # This can also be given via NETSCALER_NITRO_USER environment variable
                nitro_pass: verysecretpassword # This can also be given via NETSCALER_NITRO_PASS environment variable
                # nitro_auth_token: "098765456789098765456789"
                nitro_protocol: https # This can also be given via NETSCALER_NITRO_PROTOCOL environment variable
                validate_certs: false # This can also be given via NETSCALER_VALIDATE_CERTS environment variable
          
                # Should the module save the config after making the changes. This is optional. Default is false.
                save_config: false # This can also be given via NETSCALER_SAVE_CONFIG environment variable
          
                state: present # This is the desired state of the resource. The module will make sure that the resource is in this state. Valid values are `present`, `absent`, `enabled`, `disabled`, `imported`, `created`. However, not all modules support all the states. Refer to the module documentation for the supported states.
          
                # The following are the module parameters. Refer to the module documentation for the list of supported parameters.

felixfontein · January 3, 2024, 6:29pm

I don’t think you can. integration_config.yml is the only way to pass data (and credentials) into the tests.

felixfontein · January 3, 2024, 6:56pm

(The only exceptions are ‘cloud’ config plugins. These ship with ansible-test and the existing ones can be found here: ansible/test/lib/ansible_test/_internal/commands/integration/cloud at devel · ansible/ansible · GitHub I’m using quotes for ‘cloud’ since they also set up things not related to clouds. Right now it’s not able to add a new plugin without getting it merged into ansible-core itself, to my knowledge. I hope that eventually changes…)

sumanth-lingappa · January 4, 2024, 3:04am

OK. Thank you @felixfontein.

I feel the integration test documentation can be improved to a great extent.

For a beginner like me, more than the documentation, I am looking other collection’s repo and learning

valkiriaaquatica · April 18, 2024, 9:58pm

Hey @sumanth-lingappa just have seen your repo. Do you finally know how to pass variables securily in ansible-test integration? I’ve just tried with ansible-vault which is not compatiable, enviroment variables that do not work and using vars (works but in plain text as in yo example so not good)

Thanks in adevanced!

sumanth-lingappa · April 30, 2024, 9:20am

No @valkiriaaquatica, I did not find any way to pass the environment securely. as of now, I am generating integration_config.yml at run time before the integration tests.

valkiriaaquatica · May 12, 2024, 2:36pm

Hi @sumanth-lingappa yes, that’s what I keep doing, constructing enviroment vars as time creation and passing them to the integration_config.yml.
Thanks btw!