-
Notifications
You must be signed in to change notification settings - Fork 843
Atomic: Modify /sites/%s endpoint to rely on the privacy model
#45600
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
Open
sergeymitr
wants to merge
6
commits into
trunk
Choose a base branch
from
update/atomic-site-endpoint-is-private
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
97ee164
Atomic: Auto-adjust 'blog_public' property to match privacy model.
sergeymitr 5399786
Save option updates to log2logstash.
sergeymitr 6173623
Adjust namespace chain in function calls.
sergeymitr d9c0b63
Silence phan false-positives.
sergeymitr 229b5fc
Merge branch 'trunk' into update/atomic-site-endpoint-is-private
sergeymitr 07490bb
Do not update the '0' value.
sergeymitr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
4 changes: 4 additions & 0 deletions
4
projects/plugins/jetpack/changelog/update-atomic-site-endpoint-is-private
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| Significance: minor | ||
| Type: other | ||
|
|
||
| Atomic: Modify `/sites/%s` endpoint to rely on the privacy model, and auto-adjust local 'blog_public' option to match privacy model. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 4 additions & 0 deletions
4
projects/plugins/wpcomsh/changelog/update-atomic-site-endpoint-is-private
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| Significance: minor | ||
| Type: added | ||
|
|
||
| Atomic: Auto-adjust 'blog_public' property to match privacy model. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is interesting, I see the same approach to logging was used in another location in
wpcomshas well. Do you think that the number of log entries will be reasonable? Also, what is the purpose of logging the value changes - is it to help debug issues that might arise on individual sites? We could see whether the option was updated via sync, but not what value at what time, so I guess if the history was important it makes sense to log. 🤔There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just for general monitoring and potential debugging, we'll see if we actually need the data.
I don't expect the number to be too big. And since only Atomic is affected, it all should work pretty fast.
Removing it wouldn't be hard either, since Atomic runs on fresh Jetpack versions.