Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ansible role/playbook #31

Closed
odra opened this issue Aug 1, 2018 · 4 comments
Closed

ansible role/playbook #31

odra opened this issue Aug 1, 2018 · 4 comments
Labels
status/stale Issue considered to be stale & not likely to be worked on

Comments

@odra
Copy link

odra commented Aug 1, 2018

Hello,
Is there an ansible role and playbook to run the installation instead of running a bash script? If not, is there some kind of interest in one?

@pure-bot pure-bot bot added the notif/triage label Aug 1, 2018
@paoloantinori
Copy link
Contributor

Hi, no, we currently don't have one and it might migh be interesting evaluating one!

@rhuss
Copy link
Contributor

rhuss commented Aug 6, 2018

Thanks for the idea, but please hold on for a minute.

I'm currently changing the script which becomes only a thin wrapper is only a thin wrapper for installing the operator, so actually its more or less only about applying a DC to install the operator and the CRD itself. In the next release this will even change more when we jump to the Operator Lifecycle Manager for managing the CRD and operator.

So (and tbh), I don't see really a value of Ansible at that point, as it increase the requirements on the user side (bash is there all the time).

However, I could imagine that the operator itself uses Ansible for building up Syndesis, so the operator would then call Ansible after it has been applied.

@odra
Copy link
Author

odra commented Aug 6, 2018

Makes sense - using an operator does remove the need of an ansible playbook/role.

Do you think it makes sense to run an ansible script from the operator? I was taking a look ate the bash script and it looks to be simple enough to be "scripted" into the operator.

Another alternative would be to make this ansible script an apb and then provision a service instance from the operator.

@phantomjinx phantomjinx added status/stale Issue considered to be stale & not likely to be worked on and removed notif/triage labels Mar 4, 2022
@phantomjinx
Copy link
Contributor

Issue has been marked as stale and closed.
If it is really required then please reopen and request with justification accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/stale Issue considered to be stale & not likely to be worked on
Projects
None yet
Development

No branches or pull requests

4 participants