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

How to submit a PR for multiple but related changes #1364

Closed
pshamus opened this issue May 24, 2019 · 11 comments · Fixed by #1391
Closed

How to submit a PR for multiple but related changes #1364

pshamus opened this issue May 24, 2019 · 11 comments · Fixed by #1391
Labels
question The issue is a question.

Comments

@pshamus
Copy link
Contributor

pshamus commented May 24, 2019

I have refactored SqlDatabaseRole to function like SqlServerRole, where roles and their members can be managed. This will potentially address issues #845, #847, #1252, and #1339. The new functionality removes the auto-adding of SQL logins as database users. However, I have broken that out into a separate resource (SqlDatabaseUser) to allow more fine-grained control over the mappings (e.g. re-mapping of orphaned logins, different login and user names). Given that the new changes need to go together, what is the right process for a PR? Should I include both resource changes in the same PR?

In addition, I don't yet have unit tests for SqlDatabaseUser. Is that required for submission?

@johlju johlju added the question The issue is a question. label May 25, 2019
@johlju
Copy link
Member

johlju commented May 25, 2019

Really awesome work! 😃 👍 To make it easier for me as a maintainer I suggest sending in the new resource in a separate PR, and the other changes in a second PR. You can send in both PR's at the same time.
But if both PR's need to share new helper functions then I'm okay with having all changes in the same PR.

@johlju
Copy link
Member

johlju commented May 25, 2019

In addition, I don't yet have unit tests for SqlDatabaseUser. Is that required for submission?

Unit test is required for me to be able to merge the changes. All changes must be tested.
Also where integration tests has been added, the integration tests should be updated, or if there are no integration tests I would love for them to get added. I won't enforce integration tests if there are none today.

@pshamus
Copy link
Contributor Author

pshamus commented May 28, 2019

Perfect, thanks for the reply. I just submitted a PR for SqlDatabaseRole and will work on the unit tests for SqlDatabaseUser.

@ykuijs
Copy link
Member

ykuijs commented Jul 10, 2019

With v13.0 the SqlDatabaseRole PR has been merged, but the SqlDatabaseUser PR isn't submitted yet. How should I add users to a database without this new resource?

@johlju
Copy link
Member

johlju commented Jul 10, 2019

Oh, I lost track of that - we shouldn’t have released SqlServerDsc without that new resource. :/

@pshamus how far along are you with the new SqlDatabaseUser resource? If you don’t have time to work on it, then it’s okay, it if you have something finished, maybe I can help continue the work?

@pshamus
Copy link
Contributor Author

pshamus commented Jul 10, 2019

I don’t have unit tests yet, but the code works, as I am using it already. Can I check it in and get some help with the tests?

@johlju
Copy link
Member

johlju commented Jul 10, 2019

That is great! Please send in a PR with what you got and I will gladly help out getting tests done. 😊

@pshamus
Copy link
Contributor Author

pshamus commented Jul 12, 2019

Sounds good, will do. Should I include changes to README.md and CHANGELOG.md?

@johlju
Copy link
Member

johlju commented Jul 12, 2019

Yes please do if you can put in the time. 🙂

@johlju
Copy link
Member

johlju commented Jul 17, 2019

@ykuijs SqlDatabaseUser resource merged. Not sure we can get it released until next release window though.

@ykuijs
Copy link
Member

ykuijs commented Jul 18, 2019

No problem, as a workaround I am using v12.5 now :-)

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

Successfully merging a pull request may close this issue.

3 participants