Subdomain consolidation tickets

DOP-2630 Create dotComProd ECS environment and buckets

Subdomain consolidation tickets

DOP-2630 Create dotComProd ECS environment and buckets

This release rolls back changes made to utilize execSync and an increased buffer output configuration.

Regressions were observed in legacy builds due to execSync's changed return signature vs. exec - stderr is not populated in exit code zero cases, and stderr is the output buffer for legacy build warnings and errors.

New Features

Front End

• Bump consistent nav to v1.2.7: Updates the "Try Free" link to https://www.mongodb.com/cloud/atlas/register
• Headings now have a new icon that you can click to automatically copy the url for that heading (DOP-2393, #516).
• Hovering over the guides within a chapter card now shows a gray background to indicate that it can be clicked (DOP-2601, #512).

Parser

• OpenAPI specs may now be fetched from realm (DOP-2533, #360) with the :uses-realm: option on the openapi directive.

Improvements / Fixes

Parser

• The language server has had significant work to increase concurrency and reduce jank, and now runs the postprocessor (DOP-2546, #358) bringing diagnostic parity with builds. More work is planned, but this is a significant step forward, years in the making!
• The iOS SDK Realm SDK tab has been retitled to Swift SDK courtesy of Chris Bush (#364).
• HTTP cache now avoids re-sending requests for an hour (#363)

Decouple Staging environment from Writers staging activity

Staging buckets are part of staging stack but used by prod and staging autobuilders.

As we are working on phase 2 of autobuilder , deploying it to the staging for dev test purposes created issues with the cloudformation stack, eventually we have to delete it ( stack was drifted and importing was not successfull)

This should not happen at all, once we have a dedicated dev environment where all our dev testing will be done.Said that, since the staging buckets are used by both environments,

i am thinking moving the buckets used to stage the build ,to prod environment itself. so that anything done on the lower environments wont affect things

https://jira.mongodb.org/browse/DOP-2564

v1.1.6

Parser:

https://github.com/mongodb/snooty-parser/releases/tag/v0.11.7

Frontend:

https://github.com/mongodb/snooty/releases/tag/v0.11.19

Handle null outputs from deploy command

Parser

Added

• External link roles for the k8s migration (DOP-2556).
• rust-async and rust-sync driver tabs.
• Directives and metadata for upcoming guides work.

Changed

• Docutils 0.18 is explicitly unsupported for the moment.

Frontend

Fixed

• DOP-2489: Update Community Link #509
• DOP-2485: Fix page scrolling #505

Validating only when necessary data is available

Enable lambda deployment

Enable Dochub eventhub lambdas
Fix issue for non next gen repos validating publish branches

Tickets
DOP-2406
DOP-2407
DOP-2408

Relaxing the bucket policies to include list objects entitlements

FE 0.11.14 && 0.11.15

Parser 0.11.5

Use new version of consistent top nav

Fixing Purging issues DOP-2481
Current purge implementation is not working. for the following reaosns

• We are using dochub service id and credentials for all other services we have in the system
• We are purging by surrogate key which is implemented wrongly, unless a key is associated with a url we wont be able to use it.

Implementation includes the following

• pick ids and token based on the repo
• purge by url , urls are returned by mut publish

Upgraded parser
New buckets for node, java and go drivers