multiple_keys param

[sdodsley]

SUMMARY

Add new parameter multiple_keys to allow more than 1 access key to be created for a user, to the maximum allowed by Purity//FB. Default is false which will only allow a single access key for the user. Leaving this as the default will only allow 1 access key for the user, stopping additional keys being added on multiple runs of a playbook. Makes the module more idempotent.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

purefb_s3user.py

[RealKelsar]

Hi, I tested it now and it got some weird failure mode.

If you set multiple_keys: false and then create the S3User, it gets one API Key. After the 1st Ok run it runs into this error with each new run:

"changed": false, "msg": "Object Store User trtesting/admin: Access Key creation failed"

If i let it create a 2nd API Key, more runs with multiple_keys: false work like expected without a change or error

Snippet of the Playbook:

    - name: Create object store user (with access ID and key) 'admin'
      purestorage.flashblade.purefb_s3user:
        fb_url: "{{ fburl }}"
        api_token: "{{ apikey }}"
        name: "admin"
        account: "{{ res_obj['account'] | d(res_meta['name']) }}"
        access_key: true
        multiple_keys: false

[sdodsley]

@RealKelsar thanks for checking out the patch. I have updated this, so hopefully the error you were seeing has been resolved.

[RealKelsar]

@sdodsley we are close ;)

It works now kind of like expected, only one key gets generated and it works on the 1st try, but now it is every time a 'changed'

It does not seem to change anything, key generation time stays the same.

[sdodsley]

@RealKelsar I think that should fix it...

[RealKelsar]

Works for me!