[bruno-andrade-azion]

Summary

• Auth layer (en, pt-br):
  • The init step runs azion init --name my-auth-storage. Azion CLI 4.24.0 ignores a positional name: it asks Your application's name: with a random suggestion, so cd my-auth-storage failed for a reader who accepted it.
  • The step describes the real prompts (Choose a preset: / Choose a template:).
  • azion create variables before azion deploy replaces the root .env + azion sync step, because azion sync reads .edge/.env and never sent JWT_SECRET or BUCKET_NAME to the function.
• Vector search (en, pt-br): the tutorial splits a one-time, idempotent setup.mjs from a read-only search function.
  • The setup reuses an existing database and recovers from 14001 Name Already In Use.
  • It polls getDatabase until status is created, uses IF NOT EXISTS, and seeds only when the table is empty.
  • Before this change, the first request failed on CREATE TABLE, and every later request returned 500 on 14001.
• Vector search, the function:
  • It is index.js in the Javascript / Hello World project that the prerequisite links to. It was main.ts, a file that project does not have.
  • It uses the ES Modules export default { fetch } handler instead of the deprecated default-export function.
• Vector search, the library:
  • The page switches to @aziontech/sql, as the Azion Lib reference does.
  • It aligns the failure envelope with that reference.
  • It keeps the LangChain Vector Store/Retriever note, whose source is the May 5, 2025 release notes.

How to test

1. pnpm dev
2. Open /en/documentation/guides/application-development/data/auth-layer-object-storage-functions/ and its pt-br version, /pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/dados/camada-autenticacao-object-storage-functions/.
   • The init step runs azion init --name my-auth-storage and names the preset and template prompts.
   • The "Store the environment variables" section uses azion create variables.
   • The deploy section has no azion sync.
3. Open /en/documentation/guides/application-development/data/sql-database-vector-search/ and /pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/dados/edge-sql-vector-search/. Stages 2–4 build setup.mjs, stage 5 is the index.js search, and stage 6 runs it with azion dev.
4. Optional, with SQL Database enabled: follow the vector search tutorial end to end, then run node --env-file=.env setup.mjs twice. The second run prints Setup complete without creating anything.

Notes

• Jira: MM-16222 (T10). Epic: MM-16212.
• The package name @aziontech/sql overlaps with MM-16229 (T17), which applies the same decision to the other SQL pages.
• Not covered here, pending SME answers in MM-16194:
  • Question 87: whether Azion.env.get() reads .env under azion dev. The auth-layer page makes no claim about local env.
  • Whether Restricted blocks azion:storage.
• Checked locally, without an Azion account:
  • The @aziontech/sql 1.0.1 source agrees with the page: getDatabase returns {} for a missing name, status goes from creating to created, and a failed statement fails the whole call.
  • Under @aziontech/bundler 1.2.0, which azion dev runs:
    • the index.js extracted from the page builds with no deprecation warning;
    • the function reads the root .env;
    • Azion.Sql is undefined, so useQuery goes through the API and reads the database that setup.mjs wrote.
  • setup.mjs extracted from the page runs on Node 26 with --env-file and stops cleanly on an invalid token.
• The samples were not executed against a live account with SQL Database.
• lint:links reports auth-layer-object-storage-functions: no closing link into "functions". The same finding already exists on main.
• No permalink changes, no new dependencies.