New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 701953 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
User never visited
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Get Help app: migrate Support Content API from legacy to current

Project Member Reported by morsed@google.com, Mar 15 2017

Issue description

Push is on to migrate depended applications from legacy Support API to new API (googleapis.com to support.google.com).  Deprecated endpoints are set to be turned down in Q2.  Possibility of service outages beyond that point.  

This ticket is for research and implementation of Get Help app migration to new Support Content API. 

Support Content API announcement, with resource links: https://groups.google.com/a/google.com/forum/#!starred/support-content-announce/ujqbn3ZIPlI 

Legacy documentation: 
https://sites.google.com/a/google.com/support-content-v2/ 

New API documentation: 
https://g3doc.corp.google.com/customer_support/content/g3doc/site/support_content/integration/overview.md?cl=head 


Support Content Frontend API Migration Guide: 
https://docs.google.com/document/d/1-EBWbRxCz397Tkx2CcC875ef6CMkQPjNhFxibY-8Zdg/edit#heading=h.sc6uyeax8eis 

 

Comment 1 by morsed@google.com, Apr 22 2017

Description: Show this description

Comment 2 by morsed@google.com, Apr 22 2017

Status: Started (was: Assigned)
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fdc621807ae9a6cc4b451472a5bf5225a6e2c1e3

commit fdc621807ae9a6cc4b451472a5bf5225a6e2c1e3
Author: morsed <morsed@chromium.org>
Date: Tue Jun 06 23:11:58 2017

Get Help/HelpApp M61 release - manifest files

Support Content API Migration

Migrating both Get Help app and child HelpApp from
old googleapis.com API to new support.google.com API.

BUG= 701953 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2926733002
Cr-Commit-Position: refs/heads/master@{#477454}

[modify] https://crrev.com/fdc621807ae9a6cc4b451472a5bf5225a6e2c1e3/chrome/browser/resources/chromeos/genius_app/manifest.json
[modify] https://crrev.com/fdc621807ae9a6cc4b451472a5bf5225a6e2c1e3/chrome/browser/resources/help_app/manifest.json

Comment 4 by morsed@google.com, Jun 7 2017

Labels: -M-59 M-61
Project Member

Comment 5 by bugdroid1@chromium.org, Jun 8 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-assets/+/466a38834b9bb227df53075a5e5cc799b40bd21f

commit 466a38834b9bb227df53075a5e5cc799b40bd21f
Author: David Morse <morsed@google.com>
Date: Thu Jun 08 06:45:47 2017

Comment 6 by morsed@google.com, Jun 8 2017

Status: Fixed (was: Started)
M61 CrOS landed in 9630.0.0/61.0.3124.0
M61 Chromium landed in 9627.0.0/61.0.3123.0
Status: Verified (was: Fixed)

Sign in to add a comment