You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now if we send a Push publish request and it failed with any conflicts then we need to run the integrity checker, resolve conflicts and after that send the PP again.
The idea is use the information in the Manifest file to run the Integrity Checker in the receiver, just for the assets included in the Bundle to check if any conflicts exists before run the Handlers.
We are going to create a new filter's property to set if the Integrity Checker must run in the receiver or not, this new properties could be named something like integrity and it is going to have 3 possibles values:
-none(default): the Integrity Checker will not run before Push Publish in the receiver.
-fix: The Integrity checker will run and fix the conflicts (if any exists) in the receiver.
-notify: The Integrity Checker will run in the receiver but it will not fix the conflicts if there is any then they are notify in the sender.
The step by step to run the Integrity Checker in the receiver, when publish from the sender, will be:
Open the Push Publish dialog
Select any filter with the integrity property not equals to none.
The Bundle is generated and sent to the receiver
In the receiver the BundlePublisher gets the sender’s data from the Manifest and run the IntegrityUtil#completeCheckIntegrity method to start the Integrity Checker process.
If there are no conflicts then bundle processing continues as normal.
If conflicts are detected then it acts depending upon the filter's integrity property value:
a. If the value is equals to fix then it run the IntegrityUtil#fixConflicts method to fix the conflicts in the receiver,
and after it run the publishing.
b. If the value is equals to notify then the user will get a report with the conflicts
Tt should work for Upload bundle too.
If the integrity property value is equals to notify then the conflicts are reported showing an icon in the Status / History list next to the status message, clicking the icon will show the conflict dialog (the same use currently).
The text was updated successfully, but these errors were encountered:
freddyucv
changed the title
Run Integrity Checker before Publishing a Bundler in the receiver
Use Manifest to check integrity before ingesting bundle
Jan 27, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Right now if we send a Push publish request and it failed with any conflicts then we need to run the integrity checker, resolve conflicts and after that send the PP again.
The idea is use the information in the Manifest file to run the Integrity Checker in the receiver, just for the assets included in the Bundle to check if any conflicts exists before run the Handlers.
We are going to create a new filter's property to set if the Integrity Checker must run in the receiver or not, this new properties could be named something like
integrity
and it is going to have 3 possibles values:-none(default): the Integrity Checker will not run before Push Publish in the receiver.
-fix: The Integrity checker will run and fix the conflicts (if any exists) in the receiver.
-notify: The Integrity Checker will run in the receiver but it will not fix the conflicts if there is any then they are notify in the sender.
The step by step to run the Integrity Checker in the receiver, when publish from the sender, will be:
a. If the value is equals to
fix
then it run the IntegrityUtil#fixConflicts method to fix the conflicts in the receiver,and after it run the publishing.
b. If the value is equals to
notify
then the user will get a report with the conflictsTt should work for Upload bundle too.
If the integrity property value is equals to
notify
then the conflicts are reported showing an icon in the Status / History list next to the status message, clicking the icon will show the conflict dialog (the same use currently).The text was updated successfully, but these errors were encountered: