It's mentioned explicitly in

• /docs/authentication/ in top intro
  
• /docs/#getting-api-keys
  

entire pipeline ran and deployed. only 'issue' was pipeline feedback said complete while ecr image hadn't fully deployed yet. After a few minutes the new site build completed silently.
Dev and Prod are updated to 6.9.0 w/ accompanying theme updates as well.

Update. We have already published /docs/filtering/ page as a v1.
Can work on 'better' / more in-depth version with more/better examples too depending on demand/need.

just testing here with filters (removed chunks field just to have a smaller payload) in postman to POST v2/snapshots/:

{
  "filters": [ 
    { "field":"is_part_of.identifier", "value": "enwiki" }
  ],
  "fields": ["identifier", "namespace", "namespace.name", "namespace.identifier"]
}

Ticket T407427 created for the user signup issue.
Until that's fixed I cannot test this ticket. I mean it should work but can't confirm w/o email delivery.

@SGupta-WMF signed up with new account; user created in cognito but no email was ever sent; need to dig into potential issue there.

Spacing issues in copy sent up; pipeline ran.

ready for dev deploy to test. tallyho

bool is oversight @JWuyts-WMF
@KMontalva-WMF can we get an official list of filterable fields vs not?

The added task about updating quota numbers is now created as T404929

Related ticket T363536

Updated OP; ready @JArguello-WMF

Bumping this; @JWuyts-WMF to review (slack thread)
MR4 was closed without the copy changes ever making to prod... review and see if still need those copy changes.

We've handled this and published update. closing.

Question if 'polling' is used on session, otherwise a stale window can stay "logged in" and without a refresh user wouldn't know. Hitting Cognito's /oauth2/userInfo endpoint at an interval like 60sec and if response.status === 401 redirect to /. At that point we can display a "Your session has expired. Please log in" 'modal' box (not a modal but the alert box I forget the name of).

cc @JWuyts-WMF

For reference: mentioned in older ticket T355325#9779362

Needs to be checked on. This probably went out a while ago:

• /auth/-/merge_requests/4 closed and pointed to MR8
• /auth/-/merge_requests/8 closed and deployed.

Thanks for that PR @jberkel - team appreciates the help; I see @REsquito-WMF merged it in SDK repo.

PR9 in SDK repo was merged. Does that fulfill this ticket @KMontalva-WMF?

Also, fwiw; if it's all good - just deploy to prod whenever; no need to wait beyond eng approval.

Issues included with this Prod deploy == #9, #10, #11, #12, #13
Status == all deployed to DEV Dashboard.

Hey @jberkel, on-call ENG confirmed the account has reached 1500 requests for chunks endpoint. I'll flag it so monday the main crew can take a look and see if we can't open some requests before the monthly reset but for now not much I can do.
As for the dashboard - that seems to be a front-end caching/rendering bug that will receive a ticket to sort that out - apologies for that confusion.

/docs/changelog/ updated yesterday. ✅

I'm assuming the account has hit the snapshots limit but confirming with ENG about that and the dashboard thing; standby.

Snapshot chunking endpoints are now enabled for free accounts.

Already wrote rule for dev CTAs && Nav to rewrite to dev dash.

• done.

@jberkel It will work if the request is coming from WMCS.
If the request is coming as a free user, it will not work (yet). (see previously mentioned ticket, and also this epic T386058 for status on that fix)

@Mitar see T390556

See T389548; known issue for free user tier; in sprint now.

See T385301

It would make sense to have the namespace be exact int as that's how they're defined; i want namespace 0 or 100 for instance.
I wasn't aware of the filter ability to do >x sort of thing... part of why I want to build out that filters reference page (different convo).
So whatever makes that work on your end... cool. I just think a users intent for namespace is to identify the one they want.

Hey @Mitar those empty dirs shouldn't be created but there's a bug being worked on actively that'll fix it. There's also a talk page update about this too here.

A lot has happened since this ticket but to update:

Also should add in the "pre" Enterprise website Enterprise work; mentioned here https://www.mediawiki.org/wiki/Wikimedia_Enterprise#Past_Development

merging into OP; closing this one (dupe) ==> https://phabricator.wikimedia.org/T363536

enterprise dumps html page change review => https://gerrit.wikimedia.org/r/c/operations/puppet/+/1130196

Another filters ticket posted after this one should be merged into this OP https://phabricator.wikimedia.org/T371405

see OP ticket for this: @Cpetrillo to merge? https://phabricator.wikimedia.org/T371405

all good. thank you @bd808

also https://meta.wikimedia.org/wiki/User:CReynolds_(WMF)

can i bump 'let chuck know' to when this is in dev? @JArguello-WMF trying to get results to write marketing copy and can't until that's in.
EDIT: done; I updated OP a little.

this is similar information that should be in article form/site that i'm looking for now while drafting.

@JArguello-WMF

Does the API for HubSpot require authentication?

yes; it's mentioned in the OP & in slack thread. Bearer token is in gitlab secrets dv dotenv already

First pass to find worthy intel: (not a directive for eng ticket)

• .ENV file helpers
  • specify location of .env file
  • specify that "!" need to be escaped
  • any other issues w/ user/pass for auth should be explained
• Experienced many pip dependency errors and package installation problems even inside a .venv. Repo steps could be clearer
• re: Wikimedia's Quickstart, I found it to be sort of buggy. I wasn't able to import the modules directory with the sample repo's existing structure, and had to copy the auth.py example out into the root directory for the file to partially work. I was able to get an authenticated request, but it timed out instead of staying authenticated
• "want to split articles from Wikimedia by sources i.e. from wikipedia, wikidictionary, etc. However the API doesn't seem to support this." ?? Related to us but not sure how they had combined data from multiple projects they didn't know how to separate?
• Update PY readme: "ModuleNotFoundError: No module named 'modules'" error when running Wikimedia code example. Turns out I need to do first "export PYTHONPATH=."
• had difficulty in handling internationalization for Labels and Description limits my scope of data collection to the english wikimedia API which is not beneficial for location and linguistic specific articles, such as local villages in France or Iraq, which are written in a foreign language.
• "Wikimedia doc need better instructions about the format of the responses."

LIVE ON PROD!! cc @JArguello-WMF @ROdonnell-WMF

✅ Data Dictionary updated

Okay DEV updated. Looks good to merge into main && PROD.

RE: #4 "add GET request examples" yeah... need to make a stub ticket to get convo goin.
I'll test and get this all on dev soon. standby.

Issues still unresolved:

1. /snapshots/ docs vs api resp fields discrepancy (comment #9500552)
2. /docs/authentication/ login resp fields discrepancy (comment #9779250)
3. /authentication/ endpoints description updates comment #9779257 is all done with the exception of v1/new-password-required. This was left open for ENG to make a call on 1. if we still need that endpoint in docs, 2. what the description should be. @ROdonnell-WMF w/ updated intel here in comment 10311882. cc @HShaikh again or @prabhat to make a call please.
4. add GET request examples -- @ROdonnell-WMF updated comment here about not wanting GET requests in docs. That is definitely something I asked a LONG time ago with Stephan and (pretty sure) @prabhat. This one should be extracted out into a NEW Phab ticket for exploration. Agree? Confirm and Ruairi or I will make that happen. I don't want to let that convo die in this thread.

• parser vers updated to 1.1 for markdown backticks... merged into dev
• duped descriptions fixed; on dev
• double checking all issues to confirm completeness.

1. site openapi parser updated to run path & param descriptions through backtick checker.
2. deduping descriptions is still an issue

Couple things I noticed still @ROdonnell-WMF

• in /docs/realtime/ in /v2/articles 403 and 404 are in the wrong order
• 204 is a response code in /docs/authentication/ /v1/ token-revoke, forgot-password, forgot-password-confirm, change-password endpoints but not included with descriptors.

RE: "API Response Codes & Descriptors"
Is that 'bulky' wording for response codes something we want in every single area in docs .... or I think the original intent was to have a single location with the long descriptions (like part of data dictionary maybe) and not add all that text to every single response section in docs because it adds a lot of space. THOUGHTS? idk if in yaml we can add a text link to the response section linking to that or not... but that's an option.

Live on dev env; prod will push w/ other updates when they're ready. all done here.

MR //283

the three rows (fields) content updated on DD as of yesterday.

On PROD. nominal.

DEV test == nominal. @RThomas-WMF

this is done and deployed. cc @JArguello-WMF ty @ROdonnell-WMF

Update: new MR35 added; updated ticket desc.