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

Make sensitive Remote fields write_only #1165

Merged
merged 1 commit into from Mar 3, 2021

Conversation

daviddavis
Copy link
Contributor

fixes #8202

Please be sure you have read our documentation on creating PRs:
https://docs.pulpproject.org/contributing/pull-request-walkthrough.html

@pulpbot
Copy link
Member

pulpbot commented Mar 3, 2021

Attached issue: https://pulp.plan.io/issues/8202

@daviddavis
Copy link
Contributor Author

I'm tempted to remove the tests from this PR since they are testing functionality in DRF and not pulpcore.

Copy link
Member

@mdellweg mdellweg left a comment

Choose a reason for hiding this comment

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

Looks good so far

@bmbouter
Copy link
Member

bmbouter commented Mar 3, 2021

The tests do mostly test DRF, but they implicitly test that Pulp is configuring write_only correctly. I'm ok either way tho.

@@ -0,0 +1,2 @@
Removed sensitive fields username, password, and client key from Remote responses. These fields can
Copy link
Member

Choose a reason for hiding this comment

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

Can we escape these?

Suggested change
Removed sensitive fields username, password, and client key from Remote responses. These fields can
Removed sensitive fields ``username``, ``password``, and ``client_key`` from Remote responses. These fields can

Copy link
Member

@bmbouter bmbouter left a comment

Choose a reason for hiding this comment

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

Thank you! 👍

@daviddavis daviddavis merged commit b5e49a3 into pulp:master Mar 3, 2021
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 this pull request may close these issues.

None yet

4 participants