Show public beta notice on every aio plugin command#55
Draft
krystiannowak wants to merge 2 commits into
Draft
Conversation
phornig
approved these changes
Jun 12, 2026
1be00b1 to
1a672ea
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Show public beta notice on every aio plugin command
Context
With Edge Functions entering public beta (soft launch), every invocation of the aio plugin should display a beta notice informing users that the feature is for development/experimentation only, and production use requires prior discussion with Adobe. The notice must be acknowledged before proceeding.
Behavior
build,deploy,serve,setup,list,info,tail-logs,purge-cache,help,version.--accept-beta, even with--batch. This ensures it appears in CI/CD logs for retroactive review..aio(edgefunctions_beta_agreed=true). Subsequent runs display the notice but skip the prompt.--accept-betaflag: acknowledges the notice non-interactively, for CI/CD pipelines and automation (like--accept-licensein Oracle JDK installers). The notice is still displayed.--batchflag (on commands that have it, e.g.info): also skips the interactive prompt, since batch mode already implies non-interactive usage.Changes
src/libs/base-command.jsBETA_NOTICEconstant with the placeholder notice text (final text to be provided by PM).static baseFlagswith--accept-betaboolean flag — inherited by all commands via oclif's base flag mechanism.CONFIG_BETA_AGREED = 'edgefunctions_beta_agreed'config key, registered inBOOLEAN_CONFIGS.showBetaNotice()method called frominit():console.log(chalk.yellow(BETA_NOTICE)).--accept-betaflag,--batchflag.@inquirer/promptsconfirm(). Stores agreement in local.aioon accept; exits on decline.const { confirm } = require('@inquirer/prompts')import (@inquirer/promptsis already a dependency, used bysetup.js).src/commands/aem/edge-functions/help.js--accept-betaso CI/CD users can discover it.How agreement is stored
The agreement is stored in the local
.aioconfig file (project-level, not global) viaConfig.set(key, true, true). This is the same mechanism used bysetup.jsfor storing environment configuration. Thetruesecond argument toConfig.setmeans "store locally" (in the project's.aiofile rather than the global~/.aio).Removing the beta notice for GA
When Edge Functions exits public beta and reaches official GA, remove:
BETA_NOTICEconstant andshowBetaNotice()method frombase-command.jsawait this.showBetaNotice()call frominit()--accept-betabase flagCONFIG_BETA_AGREEDconfig key and itsBOOLEAN_CONFIGSentryhelp.jsChanged files
src/libs/base-command.js--accept-betabase flag,showBetaNotice()method,CONFIG_BETA_AGREEDconfig keysrc/commands/aem/edge-functions/help.js--accept-beta