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

MX for subdomain #187

Open
roumano opened this issue Jul 4, 2022 · 7 comments · May be fixed by #188
Open

MX for subdomain #187

roumano opened this issue Jul 4, 2022 · 7 comments · May be fixed by #188

Comments

@roumano
Copy link

roumano commented Jul 4, 2022

Actually, it's not possible to create MX record for subzone (without creating the full subzone)

@roumano roumano linked a pull request Jul 4, 2022 that will close this issue
@roumano
Copy link
Author

roumano commented Oct 7, 2022

Hi,
it's possible to merge this merge request ?

@pigay
Copy link

pigay commented Nov 20, 2022

+1

@roumano
Copy link
Author

roumano commented Nov 20, 2022

I have other evolution made on my local repository but as the owner of this role doesn't respond, I don't propose yet to community as it will only waste my time

@pigay
Copy link

pigay commented Nov 20, 2022

Maybe @bertvv could tell if he still intends to maintain this repo actively?

@bertvv
Copy link
Owner

bertvv commented Nov 21, 2022

I'm very sorry for not being more responsive to issues and PRs. It is indeed increasingly difficult to set aside the necessary time to actively maintain this role. I guess the same goes for the co-maintainers, @GR360RY and @blofeldthefish. If the Ansible community had some project like Vox Pupuli for Puppet, I would probably already have contributed this role there.

When I find the time, it is my intention to go over the PRs and merge those that are useful contributions. Unfortunately, I don't have any idea on the time frame. Remark that it's never just a case of clicking the merge button and be done with it. The codebase has become so complex that new additions may introduce regressions, may not work on all supported platforms, or has issues with coding style.

@pigay
Copy link

pigay commented Nov 22, 2022

Thanks for replying. I understand that it's a large amount of work to manage all these excellent ansible roles you have written and proposed to the community.

It was not my intention to complain loudly, but as I use this role as a submodule, I am facing the choice between being forced to wait for your repo to accept PRs and make my own fork to import changes I need from various sources (which would be a shame).

Anyway, thanks for your time and efforts.

@bertvv
Copy link
Owner

bertvv commented Nov 22, 2022

I completely understand! I did not take your comment as a complaint at all, but as a legitimate concern that you have as a user.

I don't see a possibility in the near future to work on this role, though, I'm very sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants