[ansible/artifactory] Example of API use for configuration.

[bbaassssiiee]

PR Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• Title of the PR starts with installer/product name (e.g. [ansible/artifactory])
• CHANGELOG.md updated
• Variables and other changes are documented in the README.md

What this PR does / why we need it:
While not a full implementation to solve #290 this is an example that might inspire that.
It configures repos, users and permissions.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

[gitta-jfrog]

Hello @bbaassssiiee
Apologize for not providing any feedback for long time. We are investing effort to improve it.

As part of JFrog Self-Hosted Installation, we would like to avoid from adding a code which using the REST APIs to our different installations. As this Ansible solution is dedicated only to the installation of JFrog products, adding APIs capabilities will require us to increase our maintain on this solution, and actually repeat some of the capabilities which already part of JFrog Terraform provider.

In contradict to the APIs, supporting Configuration files and bootstrapping files are indeed relevant. We should do it in a generic way, where the Ansible solution take the files as it is as forwarded it to the application (similar as we are doing in Helm Chart).

Thanks for your contribution, and I hope it more clear now what our directions to the future.

Yarden.

[bbaassssiiee]

OK thanks for the feedback