Mohamed El Mouctar Haidara

This is an overview of when multiple plays use the same roles (this is a quick test I did). It should be easy to implement by replacing the node generated...

Can you give a try to #111? I made some changes to

Yeah that's a nice idea. Will see how this can be done. This makes me think about (https://github.com/openstack/ara) that doesn't have the graph part and use ansible callbacks

The code is now cleaner. Will update the Readme with an example to integrate this in an existing project. Meanwhile, you can take how the [CLI works as an example](https://github.com/haidaraM/ansible-playbook-grapher/blob/7a92fe8e7a2701d2e27a746e405c6df162992146/ansibleplaybookgrapher/cli.py#L41-L57).

Interesting. Should be doable

Regarding this feature, do you expect to only collapse the tasks attached to the roles I guess ?

You can follow the status here: https://status.coveralls.io/?utm_source=embed

Hi @ahilmathew. See my answer here: https://github.com/Mongey/terraform-provider-kafka/issues/185#issuecomment-898935963 Since MSK cluster can't be exposed publicy, make sure you have network access from where you are running Terraform. And no need to...

Looks like MSK can't be publicly exposed so Github Actions can't reach it. From the [FAQ](https://aws.amazon.com/msk/faqs/?nc1=h_ls): > ... the only way data can be produced and consumed from an Amazon...

The issue is that currently Terraform doesn't delete the old cluster. The cluster keeps it's old name even though I apply the change. Terraform plan says that the resource will...