Add support for custom environments in CLI commands #4
+200
−11
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.
This PR implements dynamic environment detection to allow users to define and use custom environments beyond the hardcoded
dev,staging, andproductionoptions.Problem
Previously, the CLI only supported three hardcoded environments defined as a union type:
This prevented users from creating additional environments like
testing,demo, orlocal-devfor their specific workflows.Solution
The CLI now automatically detects available environments by scanning environment variables for common patterns. When users define variables following the pattern
{ENVIRONMENT}_SERVER_IP,{ENVIRONMENT}_DATABASE_NAME, etc., the CLI automatically recognizes that environment as valid.Example Usage
With a
.towardfile containing:Users can now run:
Key Changes
detectEnvironments.tsutility scans environment variables for patterns like{ENV}_SERVER_IP,{ENV}_DATABASE_NAMEEnvironmenttype from hardcoded union tostringfor unlimited flexibility.towardfile to capture all defined environments<dev | production | staging | testing>Backwards Compatibility
dev,staging,productionworkflows continue to work unchangedFixes #3.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
dl.deno.landcurl -s REDACTED(dns block)esm.ubuntu.com/usr/lib/apt/methods/https(dns block)If you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.