Vincent Batts
b0ceef0566
*: tidy and test fix
...
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2020-09-24 14:55:48 -04:00
Vincent Batts
9dca822092
*: build paths to my repo
...
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2020-09-24 14:55:48 -04:00
6885a90813
Revert "update_engine_events.go: Add a custom "InstallStarted" event."
2017-08-07 13:19:09 -07:00
3648e19ebf
Merge pull request #28 from yifan-gu/add_install_started_event
...
update_engine_events.go: Add a custom "InstallStarted" event.
2017-08-07 13:11:49 -07:00
13e4359083
update_engine_events.go: Add a custom "InstallStarted" event.
...
This can help us to know how many clusters have clicked "start upgrade",
plus those in automatic mode.
2017-08-07 13:00:40 -07:00
1925112df9
omaha: Make the trivial server to only return newer packages.
...
This is for adding related test in TCO.
2017-06-28 12:13:30 -07:00
0152a8b1b0
client: export NewAppRequest and SendAppRequest methods
...
Allow for more flexibility in constructing requests if needed.
2017-06-09 18:40:25 -07:00
a2f653da34
client: send "Complete" event in update checks
...
Needed in order to match update_engine behavior.
2017-06-09 18:40:25 -07:00
d946c1e7b2
client: disable checking for ping and event status in responses
...
Turns out CoreUpdate does not currently send <ping status="ok"> and
<event status="ok"> in responses like the protocol says it should.
2017-06-09 18:40:25 -07:00
2d48f3a029
client: send error events if update check or ping fails
...
Does not report errors when sending events since that would be cyclic.
2017-06-09 18:40:25 -07:00
41143a9d17
client: define error codes and events used by update_engine
...
Event error codes are application specific but for the sake of
simplicity lets re-use the update_engine ones where applicable.
update_engine and thus CoreUpdate only use a small subset of possible
event types so we can provide pre-defined event structs for them.
2017-06-09 18:40:25 -07:00
9ed95f2e49
protocol: fix data type for event errorcode, should be an int
2017-06-09 18:40:25 -07:00
03222d488c
client: support sending events asynchronously
...
Makes blocking and waiting for success/error optional, also allows
concurrent use of the rest of the client while events are sent.
2017-06-09 18:40:25 -07:00
c42bec118e
client: support runtime changes of app id
2017-06-07 11:29:02 -07:00
3b5d143dc5
client: add application oem attribute
2017-06-07 11:29:02 -07:00
bd1ae5648e
client: add rough example for using the client
2017-06-05 13:23:32 -07:00
1b026dfef5
client: add fuzzy timer for update check and ping interval
...
Uses the same timing parameters as update_engine.
2017-06-02 18:44:29 -07:00
c88c5916bb
client: implement exponential backoff on temporary network errors
...
Uses a fuzzy timer to reduce chance of multiple clients synchronizing.
2017-06-02 18:44:29 -07:00
c9e5a6a602
client: define default version as a constant
2017-06-02 18:44:29 -07:00
d40844181a
client: add fuzzy timer
...
For randomizing update check intervals and backoff delays to reduce
chance of DoSing the server if lots of clients start together.
2017-06-02 18:42:53 -07:00
73e12a0154
client: add support for machine-wide omaha clients
...
Uses machine id and boot id for user and session respectively, matching
the existing behavior of update_engine.
2017-05-25 13:57:28 -07:00
ad277db627
client: implement event, ping, and updatecheck
...
For simplicity one request is sent for each event/ping/check for each
application. In the future it would be wise to batch together multiple
events and multiple applications to avoid excessive chatter.
2017-05-25 13:13:10 -07:00
5a03e1d183
codes: improve app and update status error messages
2017-05-25 13:13:10 -07:00
afab572db3
protocol: change IsMachine flag to int
...
This flag is a boolean "0" or "1", with "0" as the default so keeping
the "omitempty" xml option is ok.
2017-05-25 13:13:10 -07:00
d8ad567e7f
protocol: add GetApp helper methods
2017-05-25 13:13:09 -07:00
45e1ea6221
client: report sensible errors if response is excessively large or empty
2017-05-25 13:13:09 -07:00
e6f3abe15e
client: support retrying requests after transient HTTP errors
...
Wraps failed http.Request objects in a net.Error interface.
2017-05-25 13:13:09 -07:00
b8149cc683
client: add extended http client for making omaha api requests
...
Supports encoding/decoding omaha xml and retrying on transient failures.
2017-05-25 13:13:09 -07:00
b2b975be5d
client: begin omaha client implementation
...
This first commit just covers the basic data structures.
2017-05-25 13:13:09 -07:00
036aedf2d7
protocol: remove stray Event type
...
The Event struct was split into EventRequest and EventResponse back in
75a1125f
2017-05-05 11:53:52 -07:00
a6290c1b4f
protocol: add ParseRequest and ParseResponse functions
...
For parsing and verification of of HTTP request and response bodies,
including optional checking the Content-Type field which the handler
previously didn't do.
2017-05-04 13:25:46 -07:00
6198ba9443
protocol: style fix, use "ID" and "SHA" in identifiers.
2017-05-04 13:22:27 -07:00
5f9a499a46
package: fix SHA256 attribute name, now defined by the spec.
...
The old name was my own extension and unused by anything so there aren't
any compatibility issues here.
2017-05-02 13:15:04 -07:00
79e582819b
protocol: sort xml attributes
...
A cosmetic change, though this will change the order in the XML output.
The spec lists fields alphabetically so this makes comparison easier.
2017-05-02 13:07:53 -07:00
9a796427d5
omaha: distinguish zero and unset in ping active days field
...
Unlike the other fields unset here would mean unknown rather than "0" so
we must distinguish between the two. In the end it isn't very
significant since our update server and none of our clients use these
self-reported active times, exclusively using when pings were received.
2017-04-24 13:05:53 -07:00
c7d81825c4
omaha: remove lingering references to mantle
2017-04-24 12:23:53 -07:00
4b95d8178b
omaha: update upstream doc URL
2017-04-24 12:04:41 -07:00
4d02220019
omaha: add basic but functional omaha server for testing
...
This server doesn't care about app id, versions, or really anything.
Once a payload has been set it will use it for all update requests.
2017-04-21 14:12:44 -07:00
e5eb9eb583
omaha: implement server based on OmahaHandler
...
As-is this server cannot do much and must be given an Updater
implementation to handle requests. Server.Mux is exposed to in case the
server needs to additional handlers for serving package payloads, etc.
2017-04-21 14:12:44 -07:00
f33cb66abb
omaha: add complete http handler implementation
...
The handler is driven by something implementing the 'Updater' interface.
2017-04-21 14:12:44 -07:00
2cf1d8f13e
omaha: support using status codes as error values
2017-04-21 14:12:44 -07:00
5e54ada1e9
omaha: add structure for representing a single app update
...
The protocol structures are intended for representing a collection of
apps and their updates but for a server's internal API and data store we
need to represent a self-contained app update manifest.
2017-04-21 14:12:44 -07:00
5543f86194
omaha: add helper method for computing package metadata
2017-04-21 14:12:44 -07:00
f208691b12
omaha: stop wrapping URL slice in a struct
...
Since splitting request and response structs it is no longer necessary
to work around Go's awkard handling of a `xml:"urls>url"` tag.
2017-04-21 14:12:44 -07:00
a3bc668225
omaha: add/fix missing or outdated attributes
2017-04-21 14:12:44 -07:00
75a1125f53
omaha: split request and response structures
...
Despite having common names between the request and response XML
structures the actual values which may appear in them are completely
disjoint. Splitting the types up makes the protocol easier to understand
when reading the code. When applicable, required fields like status are
passed to Add* methods.
2017-04-21 14:12:44 -07:00
ec70842bdd
omaha: rework/cleanup protocol APIs
...
- Avoid long argument lists and only pass values that are strictly
required such as status, fill in all other fields directly instead.
- Fill OS struct in requests based on local system.
- Define event and status codes as constants.
- Misc style tweaks.
2017-04-21 14:12:44 -07:00
fef283aeb6
omaha: remove XMLName from nested structures
...
The special XMLName field is only useful in the top level structs which
need something to attach the lower case tag to. On the rest the default
behavior without XMLName works just fine so it is clutter.
The datastore tags have been dropped too since they are not needed.
2017-04-21 14:12:44 -07:00
6ab36bd0dc
omaha: fix go vet complaints
...
omaha/protocol_test.go:83: ExampleOmaha_NewResponse refers to unknown identifier: Omaha
omaha/protocol_test.go:134: ExampleOmaha_NewRequest refers to unknown identifier: Omaha
2017-04-21 14:12:44 -07:00
8650026537
omaha: update file header style and file names
2017-04-21 14:12:44 -07:00
Vincent Batts
Yifan Gu