fix(applications): apply live test results and define each resource by its role by marcus-souza-azion · Pull Request #2626 · aziontech/docs

marcus-souza-azion · 2026-11-10T18:04:56Z

What & why

Related issue: 16300 and 16301.

Pages affected: 135 files:

28 of the 29 pages of the Applications section, in both languages (56 files). The Guides and tutorials hub did not change;
23 pages outside the section, in both languages (46 files);
the style guide: 5 English pages and 28 Portuguese pages (33 files).

The section's en permalinks, under /en/documentation/platform/applications/:

Applications: the overview (/), how-it-works/, quickstart/, glossary/, limits/, best-practices/, troubleshooting/
Reference: main-settings/, device-groups/, rules-engine/, websocket/, functions-instances/
Cache: cache/, cache/quickstart/, cache/expiration-and-freshness/, cache/cache-settings/, cache/cache-keys/, cache/real-time-purge/, cache/tiered-cache/
Application Accelerator: application-accelerator/, application-accelerator/quickstart/, application-accelerator/cache-variation/, application-accelerator/settings/
Image Processor: image-processor/, image-processor/quickstart/, image-processor/image-delivery/, image-processor/url-parameters/, image-processor/settings/
Outside the section, where a page repeated a fact that the tests corrected:
- 15 guides: five on cache and purge, image processing, building an application, Function Instances, origin signing, routing by country, four templates, and one migration guide;
- the Functions how-it-works/ and glossary/;
- the Azion CLI azion-config-js/ and resources/application/;
- the Connectors quickstart/;
- three use cases: application acceleration, e-commerce storefronts, and websites and APIs with a CDN.
Style guide: content/overview/, content/concept/, writing/sentence-structure/, writing/terminology/, and writing/word-choice/, plus 23 Portuguese pages that only change one term.

Each commit that changes a page carries both languages.

Part 1: corrections from live tests (10 commits)

The tests ran on one account, with the API v4 as the source of truth, plus HTTP requests, Azion CLI 4.24.0, and Azion Console read without saving. A behavior counted only after 40 consecutive answers over 60 seconds from three servers or more. The tests contradicted 25 claims of the pages, and three tests were inconclusive.

Cache cannot be turned off. The API refuses modules.cache.enabled set to false with 31001, the CLI refuses --cache false, and the Console shows the switch locked. Main Settings said "You can turn it off".
Session cookies under Forward Cookies. A denylist of session_id makes two sessions share one object, and one session receives the Set-Cookie of the other. Best practices and the cache policies guide recommended that denylist. They now recommend the allowlist, which was run in the same setup.
A Max Age of 0 sends every request to the origin. The pages promised one origin request for parallel requests and a 304 revalidation.
Bypass Cache with Tiered Cache. The layer keeps objects for the Max Age of the cache setting, not for "the minimum TTL". Eleven pages carried it.
Cache key format. Under allowlist and denylist, the query string follows @@. A purge by cache key in the documented form returned 201 and removed nothing.
Image Processor. filters:format() returns the named format whatever the Accept header. ims can sit anywhere in the query string. Without fit-in, a larger size enlarges the image. A rule with Optimize Images on a path with no image returns an empty 400.
Function Instance Args replace the defaults of the Function as a whole, not key by key.
Console and CLI. The Create Connector page ends in Save. The Cache Settings list has no ID column. azion create rules-engine has no default for --phase. With JSON output, the CLI still loses the error code in 4.24.0.
New Errors rows with the code and title the API returns: 31001, 10012, 25010, 25011, 25012, and 25024. Two more codes entered the sentences that state a refusal: 27003 for a device group name, and 29003 for a Function Instance while Functions is off.
Claims that no test supports were removed or narrowed:
- the mechanism that tied stale cache to a revalidation in progress. UPDATING stays as a value of x-cache;
- the keep-alive connection to the origin;
- the three sentences that said Azion raises a limit on request.

Part 2: each resource defined by its role (8 commits)

The review rejected "Applications is a Platform Resource that runs a reverse proxy for your Workloads". The sentence reads as a proxy with the Workloads behind it, and it is false for an Application that only runs Functions.

Applications "processes the requests received by your Workloads". The next sentence lists what an Application can do: run serverless functions, act as a reverse proxy for your origins, or combine the two.
Relations run forward. "An Application receives the requests of a Workload once that Workload's deployment sets that Application" replaces "the Workloads whose deployment sets it" on every page that carried it.
Application Accelerator "unlocks four capabilities for the cache and the rules of an Application". The old definition named only the cache key, which is false for an Application that turns it on to use Bypass Cache.
Cache "stores copies of the responses to the requests received by your Applications". A test showed that Cache also stores a 200 response that a Function builds, so "origin responses" was too narrow.
Tiered Cache adds its layer "between the data center that answers a request and your origin". Five pages said that the data center "asks the origin" after a miss in that layer, which no source supports.
Other facts from the tests of this round: under Bypass Cache, x-cache reports - or BYPASS. Creating a device group needs Application Accelerator on, or the API returns 403 and 27002. Response Phase rules run on a response that a Function builds.
Two more claims with no source left the pages: connections kept open to the origin after a miss, and "one origin fetch serves every data center" for Tiered Cache.
The glossary follows the definition of each owning page in 12 rows.

Part 3: glossary rows that defined something else (1 commit)

A glossary row is a term and the definition of that term. Four rows used an ordinary word as the term and defined the place that word holds in a configuration: Images (a usage meter), allowlist and denylist (a value of behavior), and topology (a setting). The four rows left the glossary, and their facts stay on the pages that own them.

Part 4: the request path first on an Overview (2 commits)

The review asked for the path of a request before the artifact. On the Overviews of Applications, Cache, Application Accelerator, and Image Processor, ## Request path now follows the definition block, and the structure section follows it. The anchors did not change.

A section that moves keeps its text and loses its context, so each move was checked for terms used before their definition and for a fact told twice in a row. Ten sentences changed across the four English pages. The Cache Overview needed none.

Part 5: the style guide (2 commits)

Overview pages. The mechanism comes before the specimen in the Structure list, the Template, and the reader's questions. Six rules for the definition block entered the page, from the review above.
Sentence structure. A new section, Check the prose when a section moves, carries the five checks used in Part 4.
Word choice. Two new sections: name the interface with each of its elements, and state the setting, not the path, outside a task.
Model sentences. The examples that taught "runs a reverse proxy" and "whose deployment sets it" now use the sentences of Part 2.
The Portuguese class name is recurso da plataforma. The guide wrote recurso de plataforma. The term changed in 300 places, and six headings and the four links to them changed with it.

Type of change

🆕 New content (feat)
🩹 Fix (fix) — typo, broken link, wrong information
♻️ Content update (docs) — rewrite, expansion, upkeep
🌐 Translation sync (i18n)
🏗️ Platform / structure (refactor / chore) — reviewed by UXE, no content mixed in

Author checklist

PR title follows type(scope): summary (see GOVERNANCE.md §4)
Frontmatter complete: title, description, meta_tags, namespace, permalink, last_reviewed
No legacy "edge-" product names in the copy
How-to/tutorial content includes at least one runnable, copy-paste-tested code block
Screenshots (if any) have alt text and follow image standards — no screenshot is added or changed
Internal links are relative and resolve locally — root-relative, checked with the link check and the anchor check
If any permalink changed or page moved: redirect added in this PR
i18n: pt-br updated in this PR or follow-up i18n issue created:
I ran pnpm build:local (build + frontmatter check) without errors — not run

The Azion CLI reference said `--cache false` turns Cache off for an application. Azion CLI 4.24.0 refuses it on both `azion create application` and `azion update application` with "The cache cannot be false.", the message of API error 31001. The flag rows now say Cache stays on and what `false` returns, in English and Portuguese.

…vior Live tests against API v4, Azion CLI 4.24.0 and Azion Console showed: - Cache cannot be turned off: the API refuses modules.cache.enabled set to false with 31001, and the Console switch is locked on. - Behaviors that cannot share a rule are refused by the API too, not only by the Console. - Two rules that add a request header with the same name send it to the origin once, with the value of the last rule. - The glossary follows the cache key format, the x-cache dash, the ims position, the Accept header and the Tiered Cache TTL below. - The Create Connector page ends with Save, and azion deploy serves the Application it creates even when deployments names another one by ID.

- Without Cache-Control or Expires from the origin, honor keeps the copy for the Max Age of the setting, not a default TTL. - Tiered Cache keeps objects under Bypass Cache for the Max Age of the setting, not a minimum TTL. - Request coalescing happens per server, and a second request can land on another server and report MISS again. - A cached OPTIONS key carries only the method prefix; POST carries the body hash. - Stale cache no longer claims to serve during an in-progress revalidation, and the DEL removal block is gone: the domain refuses DEL with 403 and DELETE never removes the copy. - The Cache Settings list has no ID column.

- Cache keys: under allowlist and denylist the query string follows @@; under all it stays before @@, and the Cookie header follows @@ as it arrived. Image Processor keys read ...@@?ims=880xwebp, and a purge in the old ...?ims=...@@ form removes nothing. - A derived image shares a key across sizes unless the cache setting varies by the ims query string. - Cache setting names are unique per Application (10012), a tiered_cache object without topology gets nearest-region, and 21013 covers every cookie, device group, query string or method variation without Application Accelerator. - Console: Large file optimization and Tiered Cache turn off Honor cache policies; the Application Accelerator section shows only while it is on. - Tiered Cache topology points to the API reference for accepted values.

- An Application passes POST, PUT, PATCH, DELETE and OPTIONS to the origin with or without Application Accelerator; it makes POST and OPTIONS responses cacheable. - A Max Age of 0 keeps the cache path but sends every request to the origin: no coalescing, no 304 revalidation. - Cache key examples follow the @@? format for allowlist and denylist, POST keys carry the post prefix, and OPTIONS keys only the method. - The 21013 refusal covers query string, cookie, device group and method variations; the Console section shows only while the Feature is on. - Tiered Cache under Bypass Cache keeps the Max Age of the setting.

- filters:format() returns the named format whatever Accept header the request carries; forcing Accept: image/webp sends WEBP to every client. - ims can sit anywhere in the query string; an unparseable value returns the source image with x-ims: Enabled. - Without fit-in, a larger requested size enlarges the image. - A rule with Optimize Images on a non-image path fails with an empty 400. - Without a cache setting, the Application's cache keeps no derived image, and Image Processor answers repeats from its own cache. - Key examples follow the ...@@?ims=880xwebp format, orig is noted as not honored on every URL, and the API v3 switch note covers the websocket field.

- Main Settings: Cache cannot be turned off (31001, new Errors row), and 21013 covers cookie and device group variations too. - Rules Engine: Errors gain 25010, 25011, 25012 and 25024; ${remote_port} is the client's TCP source port; finish_request_phase is API and CLI only; azion create rules-engine has no --phase default; the geoip variables drop the unsourced base names. - Device Groups: names take letters and numbers only (27003). - WebSocket: Connection may carry upgrade in any case or in a list. - Function Instances: instance Args replace the Function defaults as a whole, and the API refuses an instance while Functions is off (29003).

- Limits drop the claims that a bound rises on request. - Best practices: allowlist the session cookie under Forward Cookies (a denylist shares one object and leaks Set-Cookie between sessions); drop the TTL-of-0 and ims-position practices; scope the Accept header practice to clients that display WEBP. - Troubleshooting: the dash in x-cache appears only while Application Accelerator is on; new entries for an untransformed image and for an empty 400 on non-image paths; fit-in and cache entries follow the observed behavior; Azion CLI 4.24.0 still loses the error code in JSON output.

Args set on a Function Instance replace the default Args of the Function entirely: a key the instance leaves out is absent, not kept at its default. The defaults apply only to an instance with no Args.

Pages outside the Applications section repeated facts that live tests contradicted: - Tiered Cache TTL under Bypass Cache, the 0-second Max Age, the methods Application Accelerator adds, and the keep-alive claim (architecture, use cases, Marketplace templates). - The x-cache dash, POST and OPTIONS keys, and the Image Processor key format (MCP cache testing, cache and purge guides). - The session-cookie allowlist under Forward Cookies (cache policies guide). - Cache cannot be turned off (Build journey). - The origin TTL fallback, the Create Connector Save button, the Cache Settings list columns, the geoip base names, and azion deploy with deployments (templates, connector guides, azion.config.js).

…s forward The Overview said Applications "runs a reverse proxy for your Workloads". That reads as a proxy with the Workloads behind it, and it is false for an Application that only runs Functions. - Applications now "processes the requests received by your Workloads", and the next sentence lists what an Application can do: run serverless functions, act as a reverse proxy for your origins, or combine the two. - The concept names the Function behind a serverless function, and running code leaves the list of what the proxy does. - The relation with a Workload runs forward: an Application receives the requests of a Workload once that Workload's deployment sets that Application. - How Applications works opens with a layer that can also build the response with no server behind it, and both pages say that a Function can answer a request with no Connector. - The glossary rows follow the definition of each owning page: Cache, cache setting, Real-Time Purge, Tiered Cache, Image Processor, derived image, source image, device group, Function Instance, Main Settings, Optimize Images, and Rules Engine.

The quickstart said you "bind" the Application to the Workload. The operation is the deployment of the Workload, which sets the Application. Each sentence that carries a relation now names the element that makes it: a rule sets the Connector, and the deployment sets the Application.

- Cache "stores copies of the responses to the requests received by your Applications". The definition no longer says "origin responses": Cache also stores a response that a Function builds, when a rule applies a cache setting. - Cache is always on in an Application, as Main Settings already states. - Tiered Cache sits between the data center that answers a request and the origin, and a miss goes to that layer before the request goes to the origin. - Under Bypass Cache, x-cache reports "-" or BYPASS. - Expiration and freshness drops the sentence about connections kept open to the origin, which no source supports, and the purge sentence holds when a second layer still has a copy.

- A cache setting is a set of values that tell Cache how to store and serve a response, and it belongs to one Application. - Tiered Cache adds its layer between the data center that answers a request and your origin. The page no longer says that the data center asks the origin after a miss in that layer. - Real-Time Purge: the next request reaches the origin once the object is in neither Cache nor Tiered Cache. - Cache keys: on a miss, the origin or a Function builds the response, the BYPASS row notes that a bypassed response can report "-", and the sort_enabled sentence leaves the table cell that described "all".

… it unlocks The definition said Application Accelerator "adds parts of a request beyond the URL to the cache key". That is false for an Application that turns it on only to use Bypass Cache or a Max Age below 60 seconds. The first sentence now states the role its capabilities share, and the next ones list them: cache variation, cached POST and OPTIONS responses, a Max Age below 60 seconds, and further Rules Engine behaviors and variables. The four pages use the same definition, and a device group is defined as on its own page.

…essor pages The definition of Image Processor stays. The Overview now says that Image Processor can convert an image to a format the browser accepts even with no ims query string, so the block holds for a request that carries none. The other edits tell relations forward, link first mentions, and keep one finite verb per clause where a sentence ran long. The eight example images of URL parameters and their captions are unchanged.

…ns definition - WebSocket Proxy: the connection passes through an Application that acts as a reverse proxy for the origin. - Function Instance: the entity binds one Function to one Application or one Firewall, and a rule with Run Function invokes it. - Device Groups: the Feature groups the requests received by an Application, and a device group requires Application Accelerator. The API refuses to create one while it is off, with 403 and error 27002. - Rules Engine: a rule applies to a request or to its response, a value such as ${status} exists once the origin or a Function answers, and the Workload receives the request. - Main Settings: a rule invokes a Function Instance.

- Limits opens with what an Application does, "processes the requests received by your Workloads", and tells its relation with a Workload forward. - Best practices points to the Functions practices, defines a device group as its own page does, and describes Tiered Cache without the claim that one origin fetch serves every data center. - Troubleshooting: a bypassed request carries "-" or BYPASS in x-cache, a cache setting acts only after a rule applies that cache setting, and the Application Accelerator entry uses its new definition.

…ing else A glossary row is a term and the definition of that term. Four rows used an ordinary word as the term and defined the place that word holds in a configuration: - Images: a usage meter, where the reader expects what an image is. - allowlist and denylist: a value of the behavior field. - topology: a setting of Tiered Cache. The facts the rows carried stay on the pages that own them: Pricing, Application Accelerator settings, Cache variation, Tiered Cache, and the Errors table of Cache settings. The Terms bullet of the Application Accelerator Overview no longer names allowlist and denylist as glossary terms.

…n the Overview A leadership review asked for the path of a request first: the reader sees how a request reaches an Application before the rule that acts on it. The Request path section now follows the definition block, and Rule structure follows it. The move changed the prose in four places, because the path now comes before the section that used to introduce its terms: - The opening of Request path no longer repeats the relation sentence that closes the definition block, now four lines above it. - A behavior is defined where the path first uses the word. - "a Set Cache Policy rule" and "a Set Connector rule" read "a rule with" the behavior, since the reader has not yet seen a behavior as a part of a rule. Every other line only changed place: the diagram, the JSON specimen and the anchors are unchanged.

The Overviews of Cache, Application Accelerator and Image Processor now follow the order of the Applications Overview: the Request path section comes right after the definition block, and the structure section follows it. Each move ran the checks for a section that changes place: - Cache: no sentence changed. The definition block already introduces the cache setting and the rule that applies it. - Application Accelerator: the path no longer leans on "the query-string control", which the structure section introduces, and the bullet on allowlist, denylist and all says what each value does. - Image Processor: the opening of the path no longer repeats the definition block above it, the link to Application Accelerator moved to its new first mention, and the cache setting is linked where the path first names it. Every other line only changed place: the diagrams, the JSON specimens and the anchors are unchanged.

… definition and interface rules A leadership review of the Applications Overview asked for the path of a request before the artifact, and rejected the definition "runs a reverse proxy for your Workloads". The guide now follows both. Overview pages (content/overview): - The mechanism comes before the specimen in the Structure list, in the Template and in the reader's questions. The specimen no longer has to sit within the first screen. - Six rules for the definition block: every word of position agrees with the request path, the verb covers everything the Platform Resource does, the definition is read as a reader from the market reads it, a relation between two Platform Resources is told forward, the concept is chosen with care, and a concept names the Platform Resource that provides it. Sentence structure and terminology: - A new section, Check the prose when a section moves, with five checks and the example from the Applications Overview. - The model sentences use "processes the requests received by your Workloads" and the relation told forward. Word choice: - Two new sections: name the interface with each of its elements, and state the setting, not the path, outside a task. The Overview and Concept rules against instructing link the second one. English and Portuguese carry the same changes.

The Portuguese name of the Platform Resource class is "recurso da plataforma". The guide wrote "recurso de plataforma", while the Applications section and most Portuguese pages write the form with "da". - The term changes in 300 places: 298 in the Portuguese guide and 2 in the English terminology page, which quotes it. - Six headings carry the term, so their anchors change, and the four links to those anchors follow. - The two sentences that quote the sidebar label keep "Recursos de Plataforma", because the navigation still shows that label.

* origin/main: (22 commits) docs(terraform): rewrite the samples for provider v2.10.0 (#2557) chore(deploy): promote docs-v2.4.4 to production (#2631) chore(main): release docs 2.4.4 (#2627) chore(deploy): promote docs-v2.4.3 to production (#2617) fix(applications): apply live test results and define each resource by its role (#2626) chore(main): release docs 2.4.3 (#2616) docs(applications): review the Applications section and apply the updated writing rules (#2615) chore(deps): bump npm and GitHub Actions dependencies (#2590) chore(deploy): promote docs-v2.4.2 to production (#2610) chore(main): release docs 2.4.2 (#2609) docs(style-guide): align the guide with the shipped sections and settle its open rules (#2600) chore(deploy): promote docs-v2.4.1 to production (#2569) chore(main): release docs 2.4.1 (#2568) chore(deploy): promote docs-v2.4.0 to production (#2560) docs(workloads): document custom page assignment with azion workload-deployment (#2564) docs(templates): reconcile Console Deploy links with the current catalog (#2563) docs(applications): fix rewrite argument, certificate API, workload domains, and connector CLI (#2562) docs(style-guide): review the EN style guide against the naming catalog (MM-16284) (#2561) docs(marketplace): fix invalid Arguments JSON in 7 integration guides (#2559) docs(runtime): fix broken example code in the Runtime reference (#2556) ... # Conflicts: # apps/docs/src/content/docs/en/pages/main-menu/reference/build/edge-application/first-steps.mdx # apps/docs/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/edge-app-primeiros-passos.mdx

…l-cli-configs * origin/main: (22 commits) docs(terraform): rewrite the samples for provider v2.10.0 (#2557) chore(deploy): promote docs-v2.4.4 to production (#2631) chore(main): release docs 2.4.4 (#2627) chore(deploy): promote docs-v2.4.3 to production (#2617) fix(applications): apply live test results and define each resource by its role (#2626) chore(main): release docs 2.4.3 (#2616) docs(applications): review the Applications section and apply the updated writing rules (#2615) chore(deps): bump npm and GitHub Actions dependencies (#2590) chore(deploy): promote docs-v2.4.2 to production (#2610) chore(main): release docs 2.4.2 (#2609) docs(style-guide): align the guide with the shipped sections and settle its open rules (#2600) chore(deploy): promote docs-v2.4.1 to production (#2569) chore(main): release docs 2.4.1 (#2568) chore(deploy): promote docs-v2.4.0 to production (#2560) docs(workloads): document custom page assignment with azion workload-deployment (#2564) docs(templates): reconcile Console Deploy links with the current catalog (#2563) docs(applications): fix rewrite argument, certificate API, workload domains, and connector CLI (#2562) docs(style-guide): review the EN style guide against the naming catalog (MM-16284) (#2561) docs(marketplace): fix invalid Arguments JSON in 7 integration guides (#2559) docs(runtime): fix broken example code in the Runtime reference (#2556) ...

…e-auth-vector-tutorials * origin/main: (22 commits) docs(terraform): rewrite the samples for provider v2.10.0 (#2557) chore(deploy): promote docs-v2.4.4 to production (#2631) chore(main): release docs 2.4.4 (#2627) chore(deploy): promote docs-v2.4.3 to production (#2617) fix(applications): apply live test results and define each resource by its role (#2626) chore(main): release docs 2.4.3 (#2616) docs(applications): review the Applications section and apply the updated writing rules (#2615) chore(deps): bump npm and GitHub Actions dependencies (#2590) chore(deploy): promote docs-v2.4.2 to production (#2610) chore(main): release docs 2.4.2 (#2609) docs(style-guide): align the guide with the shipped sections and settle its open rules (#2600) chore(deploy): promote docs-v2.4.1 to production (#2569) chore(main): release docs 2.4.1 (#2568) chore(deploy): promote docs-v2.4.0 to production (#2560) docs(workloads): document custom page assignment with azion workload-deployment (#2564) docs(templates): reconcile Console Deploy links with the current catalog (#2563) docs(applications): fix rewrite argument, certificate API, workload domains, and connector CLI (#2562) docs(style-guide): review the EN style guide against the naming catalog (MM-16284) (#2561) docs(marketplace): fix invalid Arguments JSON in 7 integration guides (#2559) docs(runtime): fix broken example code in the Runtime reference (#2556) ...

* origin/main: fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612) docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611) docs(guides): make the auth layer and vector search tutorials runnable (#2566) chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637) fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565) docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567) docs(terraform): rewrite the samples for provider v2.10.0 (#2557) chore(deploy): promote docs-v2.4.4 to production (#2631) chore(main): release docs 2.4.4 (#2627) chore(deploy): promote docs-v2.4.3 to production (#2617) fix(applications): apply live test results and define each resource by its role (#2626)

…-main * origin/main: (21 commits) feat(nav): give every breadcrumb crumb a page and make CLI commands runnable (#2636) fix(cli): drop azion update workload-deployment, which the CLI does not expose (#2639) docs(terminology): retire Edge Node, module, and add-on from current pages (#2618) docs(migration): share the repeated migration-guide procedures as partials (#2619) fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612) docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611) docs(guides): make the auth layer and vector search tutorials runnable (#2566) chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637) fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565) docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567) docs(terraform): rewrite the samples for provider v2.10.0 (#2557) chore(deploy): promote docs-v2.4.4 to production (#2631) chore(main): release docs 2.4.4 (#2627) chore(deploy): promote docs-v2.4.3 to production (#2617) fix(applications): apply live test results and define each resource by its role (#2626) chore(main): release docs 2.4.3 (#2616) docs(applications): review the Applications section and apply the updated writing rules (#2615) chore(deps): bump npm and GitHub Actions dependencies (#2590) chore(deploy): promote docs-v2.4.2 to production (#2610) chore(main): release docs 2.4.2 (#2609) ...

* commit '7aa84b1d0': (22 commits) docs(nav): apply the review of the orphan-page triage feat(nav): give every breadcrumb crumb a page and make CLI commands runnable (#2636) fix(cli): drop azion update workload-deployment, which the CLI does not expose (#2639) docs(terminology): retire Edge Node, module, and add-on from current pages (#2618) docs(migration): share the repeated migration-guide procedures as partials (#2619) fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612) docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611) docs(guides): make the auth layer and vector search tutorials runnable (#2566) chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637) fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565) docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567) docs(terraform): rewrite the samples for provider v2.10.0 (#2557) chore(deploy): promote docs-v2.4.4 to production (#2631) chore(main): release docs 2.4.4 (#2627) chore(deploy): promote docs-v2.4.3 to production (#2617) fix(applications): apply live test results and define each resource by its role (#2626) chore(main): release docs 2.4.3 (#2616) docs(applications): review the Applications section and apply the updated writing rules (#2615) chore(deps): bump npm and GitHub Actions dependencies (#2590) chore(deploy): promote docs-v2.4.2 to production (#2610) ...

* origin/main: (24 commits) chore(nav): count only visible rows toward the navcheck soft max (#2640) docs(nav): triage the pages outside the navigation (#2593) fix(guides): match the QStash variable and the Functions usage response to the code (#2571) feat(nav): give every breadcrumb crumb a page and make CLI commands runnable (#2636) fix(cli): drop azion update workload-deployment, which the CLI does not expose (#2639) docs(terminology): retire Edge Node, module, and add-on from current pages (#2618) docs(migration): share the repeated migration-guide procedures as partials (#2619) fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612) docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611) docs(guides): make the auth layer and vector search tutorials runnable (#2566) chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637) fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565) docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567) docs(terraform): rewrite the samples for provider v2.10.0 (#2557) chore(deploy): promote docs-v2.4.4 to production (#2631) chore(main): release docs 2.4.4 (#2627) chore(deploy): promote docs-v2.4.3 to production (#2617) fix(applications): apply live test results and define each resource by its role (#2626) chore(main): release docs 2.4.3 (#2616) docs(applications): review the Applications section and apply the updated writing rules (#2615) ...

…y-filter-removal * origin/main: (24 commits) chore(nav): count only visible rows toward the navcheck soft max (#2640) docs(nav): triage the pages outside the navigation (#2593) fix(guides): match the QStash variable and the Functions usage response to the code (#2571) feat(nav): give every breadcrumb crumb a page and make CLI commands runnable (#2636) fix(cli): drop azion update workload-deployment, which the CLI does not expose (#2639) docs(terminology): retire Edge Node, module, and add-on from current pages (#2618) docs(migration): share the repeated migration-guide procedures as partials (#2619) fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612) docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611) docs(guides): make the auth layer and vector search tutorials runnable (#2566) chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637) fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565) docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567) docs(terraform): rewrite the samples for provider v2.10.0 (#2557) chore(deploy): promote docs-v2.4.4 to production (#2631) chore(main): release docs 2.4.4 (#2627) chore(deploy): promote docs-v2.4.3 to production (#2617) fix(applications): apply live test results and define each resource by its role (#2626) chore(main): release docs 2.4.3 (#2616) docs(applications): review the Applications section and apply the updated writing rules (#2615) ...

- static-cache and dynamic-and-static-file-optimization: keep the correction from #2626. When the origin sends no cache settings, the template applies the Max Age of the cache setting, not a default TTL. - framework-next (en and pt-br): point the static exports link to the renamed heading anchor. - edge-function-starter-kit: drop "Products menu" from the Console path, as #2596 does. - langgraph-template: link the backend variables section by its anchor. - Docusaurus and pt-br LangGraph descriptions: trim to 160 characters.

Main rewrote the Applications section from live tests (#2615, #2626), so the conflicted pages take main's text. The CORS and modernize pages keep this PR's change, since main still tied them to Application Accelerator.

Conflicts resolved per block: - Template guides (10 en + 10 pt-br): keep this branch's rewritten Applications steps, which already use the Console path from #2596. - azion-starter-kit (en, pt-br): keep this branch's structure and carry #2626's fix into it: when the origin sends no cache settings, the template uses the Max Age of the cache setting, not a default TTL. - Templates overview (en, pt-br): keep main's Astro rows from #2595 and this branch's azion/azion-starter Deploy slug. - liveness-detection (en, pt-br): keep this branch's deletion; its URL redirects already exist in redirects/{en,pt-br}/01.json. - nav/redirects.json: main's version without the liveness entry, since lint-navcheck rejects an entry whose page is gone.

marcus-souza-azion added 23 commits November 9, 2026 19:33

fix(functions): state that instance Args replace the defaults as a whole

c2e00f4

Args set on a Function Instance replace the default Args of the Function entirely: a key the instance leaves out is absent, not kept at its default. The defaults apply only to an instance with no Args.

marcus-souza-azion requested a review from a team November 10, 2026 18:04

marcus-souza-azion requested a review from a team as a code owner November 10, 2026 18:04

github-actions Bot assigned marcus-souza-azion Nov 10, 2026

marcus-souza-azion merged commit 1f841e4 into main Nov 10, 2026
10 checks passed

marcus-souza-azion deleted the fix/applications-review-p2 branch November 10, 2026 18:22

github-actions Bot mentioned this pull request Nov 10, 2026

chore(main): release docs 2.4.4 #2627

Merged

bruno-andrade-azion mentioned this pull request Nov 11, 2026

docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment #2567

Merged

9 of 14 tasks

bruno-andrade-azion mentioned this pull request Nov 11, 2026

docs(migration): share the repeated migration-guide procedures as partials #2619

Merged

9 of 14 tasks

bruno-andrade-azion mentioned this pull request Nov 11, 2026

docs(terminology): retire Edge Node, module, and add-on from current pages #2618

Merged

9 of 14 tasks

marcus-souza-azion mentioned this pull request Nov 11, 2026

docs(workloads): review the Workloads section with the style guide and correct it from live tests #2570

Merged

11 of 14 tasks

bruno-andrade-azion mentioned this pull request Nov 12, 2026

docs(applications): drop the Lua-only claim for Response Phase functions (MM-16231) #2576

Closed

marcus-souza-azion mentioned this pull request Nov 12, 2026

docs(templates): migrate the legacy template guides to the current guide pattern #2597

Merged

7 of 14 tasks

bruno-andrade-azion mentioned this pull request Nov 12, 2026

docs(applications): Run Function needs only Functions; fix WEBP and CORS prerequisites #2580

Merged

8 of 14 tasks

Navigation Menu

Repository navigation

fix(applications): apply live test results and define each resource by its role - #2626

fix(applications): apply live test results and define each resource by its role#2626
marcus-souza-azion merged 23 commits into
mainfrom
fix/applications-review-p2

marcus-souza-azion commented Nov 10, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Milestone

Development

Uh oh!

1 participant

Conversation

marcus-souza-azion commented Nov 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What & why

Type of change

Author checklist

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Milestone

Development

Uh oh!

1 participant

marcus-souza-azion commented Nov 10, 2026 •

edited

Loading