Support the use of configuration source remote and inline at the same time

[morningspace]

For the configuration source, we have two options, remote and inline, which are now mutual exclusive. Can we support the use of both at the same time? The reason for that:

The remote option would be more useful in real projects, as usually people will run Ansible automation using a bunch of well-organized yaml stuff, rather than a single playbook.yml file. The inline option would be more likely for demo purpose.

However, there is one use case that probably can lead us to use both remote and inline at the same time. When call one or more roles as reusable building blocks from somewhere such as git repo or ansible galaxy, people often create playbook on top of that w/ some additional twists. This playbook may not be part of the existing contents in repos, but instead, is created on the fly, which can nicely be implemented by the inline option.

[morningspace]

@fahedouch Just to confirm:

According to https:/multicloudlab/crossplane-provider-ansible/blob/main/internal/ansible/ansible.go#L245-L246, I assume that the current implementation will not support the case logged in this issue, i.e.: playbookInline calls roles retrieved from a remote repo, right?

Also, what will happen when people define playbookInline and playbooks at the same time. This if branch seems haven't been covered yet.

P.S.: It will be fine if that has been implemented yet. We can update it in the coming releases.

[fahedouch]

Hey @morningspace ,

Yes the actual release do not support remote and inline at the same time. We try add gradually this features :)