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

Improvements around changing owners #792

Merged
merged 9 commits into from
Dec 12, 2016
Merged

Conversation

hasegeli
Copy link
Contributor

No description provided.

@hasegeli
Copy link
Contributor Author

Any luck looking at this? It would be better to do so, before releasing the change_ownership argument. The changes only look complicated because of re-indentation.

Copy link
Contributor

@DavidS DavidS left a comment

Choose a reason for hiding this comment

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

Besides the backwards compatibility issue, it would be great to keep unrelated changes (like the resource titles) out of the commit to make the change more understandable.

$tablespace = undef,
$template = 'template0',
$encoding = $postgresql::server::encoding,
$locale = $postgresql::server::locale,
$istemplate = false,
$connect_settings = $postgresql::server::default_connect_settings,
$change_ownership = false,
Copy link
Contributor

Choose a reason for hiding this comment

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

Removing this parameter is a breaking change that might cause existing configurations to break. It is better for users to accept the parameter, but not act on it, except for emitting a warning that it will go away. Newer versions of stdlib have a deprecation method to do so in a friendly way.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think this argument has been released yet. Do you think it is still necessary to accept it?

Copy link
Contributor

@DavidS DavidS Mar 7, 2017

Choose a reason for hiding this comment

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

For reference, this is a revert of 82c6716 which indeed was never released.

@hasegeli hasegeli force-pushed the master branch 4 times, most recently from b9897bb to 33e8133 Compare November 28, 2016 11:22
@hasegeli
Copy link
Contributor Author

I made the commits really clean by first reverting the existing changing owner implementation.

This reverts commit 82c6716.  It will
be added back with a cleaner design with the following commits.
@hasegeli hasegeli force-pushed the master branch 2 times, most recently from 3b5dbbb to c0ff556 Compare November 28, 2016 11:31
This can be considered a bug fix, because the old names would conflict
when there are schemas with the same name on different databases.
This also automatically requires the owner role on the database class.
@DavidS
Copy link
Contributor

DavidS commented Nov 28, 2016

This looks SO MUCH better! 🎉

You do seem to have missed one place in the tests where the expected title has changed.

I fully expect @ntpttr be satisfied with the changes too, but he should be aware of them.

@hasegeli
Copy link
Contributor Author

I fixed it. Thank you for the review.

@eputnam eputnam merged commit 169c609 into puppetlabs:master Dec 12, 2016
@hasegeli
Copy link
Contributor Author

Thank you for looking at it.

cegeka-jenkins pushed a commit to cegeka/puppet-postgresql that referenced this pull request Feb 3, 2022
Improvements around changing owners
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants