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

Added support for postgresql_privs #134

Closed
wants to merge 3 commits into from

Conversation

ArmiT
Copy link

@ArmiT ArmiT commented Dec 22, 2015

No description provided.

@@ -38,6 +38,9 @@ postgresql_users: []
# List of user privileges to be applied (optional)
postgresql_user_privileges: []

# List of privileges to be applied (optional)
postgresql_privileges: []
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as to avoid being misleading perhaps this should be postgresql_db_priveleges?

- Merged together privileges.yml and users_privileges.yml
- Removed related include and tag from main.yml
- Added data for test
- Changed description
@lhoss
Copy link

lhoss commented Mar 31, 2016

@ArmiT possible to get conflicts resolved with latest master?
with the hope we can get this merged

@gclough
Copy link
Collaborator

gclough commented Apr 6, 2018

Is this the same as #181? Which one should be merged?

@aoyawale
Copy link
Contributor

aoyawale commented Apr 9, 2018

probably this one but, is old and still needs work.

Copy link
Contributor

@nchudleigh nchudleigh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in here, would love to get this feature out current have a hack work around in my config.

@@ -38,6 +38,9 @@ postgresql_users: []
# List of user privileges to be applied (optional)
postgresql_user_privileges: []

# List of database privileges to be applied (optional)
postgresql_db_priveleges: []
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo

Suggested change
postgresql_db_priveleges: []
postgresql_db_privileges: []

type: "{{ item.type | default(\"table\") }}"
sudo: yes
sudo_user: "{{postgresql_admin_user}}"
with_items: postgresql_db_priveleges
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo

Suggested change
with_items: postgresql_db_priveleges
with_items: postgresql_db_privileges

@@ -17,3 +17,11 @@ postgresql_users:
postgresql_user_privileges:
- name: baz
db: foobar

postgresql_db_priveleges:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo

Suggested change
postgresql_db_priveleges:
postgresql_db_privileges:

@nchudleigh
Copy link
Contributor

I think all the naming here should really be simplified down to privs given that the underlying module is called privs.

https://docs.ansible.com/ansible/latest/modules/postgresql_privs_module.html

@nchudleigh
Copy link
Contributor

@gclough @jlozadad If I open another PR consolidating #181 and #134 with conflicts and naming issues resolved can I get a review sometime soon?

@gclough
Copy link
Collaborator

gclough commented Apr 9, 2019

@nchudleigh , in short, yes. I've got some time to help with this project, and have already cleaned up a lot of old PR's. There are also some new helpers that can review/comment.

@RCM7
Copy link
Collaborator

RCM7 commented Sep 5, 2019

@nchudleigh did you end up opening another PR? I'm looking forward to having this. Can also try to contribute if needed.

@nchudleigh
Copy link
Contributor

nchudleigh commented Sep 6, 2019

@RCM7 No, I got frustrated with the pace of the maintainers and stopped contributing to this project. I went with an approach of using the core ansible postgres modules and found that was good enough for my use-case.

@RCM7
Copy link
Collaborator

RCM7 commented Sep 10, 2019

@nchudleigh yeah I ended up doing the same !

@egmont1227
Copy link
Contributor

Related to Issue #175

@Pyton
Copy link

Pyton commented Sep 10, 2021

Any progress on this?

Copy link

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

@github-actions github-actions bot added the stale label Aug 28, 2024
Copy link

This pr has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.

@github-actions github-actions bot closed this Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants