LANGUAGE V1 · FROZEN REFERENCE
Capability registry
274 results · Page 20 of 23
vercelenvironment variables
supported — Laygent v1 implements environment variables in its vercel target.
Requirements and limitations
- Id
- vercel.environment_variables
- Status
- supported
- Aliases
- vercel env
- environment variable
- deployment secret
- runtime config
- environment variables
- vercel environment variables
- use environment variables
- add environment variables
- support environment variables
- Evidence
- integrations.py OAuth and publishing.py Vercel project/deployment flow
- Limitation
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
vercelfirewall
unsupported — Laygent v1 does not implement firewall in its vercel target.
Requirements and limitations
- Id
- vercel.firewall
- Status
- unsupported
- Aliases
- firewall
- vercel firewall
- use firewall
- add firewall
- support firewall
- Evidence
- Limitation
- Laygent v1 does not implement firewall in its vercel target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
vercelflags
unsupported — Laygent v1 does not implement flags in its vercel target.
Requirements and limitations
- Id
- vercel.flags
- Status
- unsupported
- Aliases
- flags
- vercel flags
- use flags
- add flags
- support flags
- Evidence
- Limitation
- Laygent v1 does not implement flags in its vercel target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
vercelgithub link
supported — Laygent v1 implements github link in its vercel target.
Requirements and limitations
- Id
- vercel.github_link
- Status
- supported
- Aliases
- github link
- vercel github link
- use github link
- add github link
- support github link
- Evidence
- integrations.py OAuth and publishing.py Vercel project/deployment flow
- Limitation
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
vercelmonorepo deployment
unsupported — Laygent v1 does not implement monorepo deployment in its vercel target.
Requirements and limitations
- Id
- vercel.monorepo_deployment
- Status
- unsupported
- Aliases
- monorepo deployment
- vercel monorepo deployment
- use monorepo deployment
- add monorepo deployment
- support monorepo deployment
- Evidence
- Limitation
- Laygent v1 does not implement monorepo deployment in its vercel target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
vercelmulti service
unsupported — Laygent v1 does not implement multi service in its vercel target.
Requirements and limitations
- Id
- vercel.multi_service
- Status
- unsupported
- Aliases
- multi service
- vercel multi service
- use multi service
- add multi service
- support multi service
- Evidence
- Limitation
- Laygent v1 does not implement multi service in its vercel target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
verceloauth connection
supported — Laygent v1 implements oauth connection in its vercel target.
Requirements and limitations
- Id
- vercel.oauth_connection
- Status
- supported
- Aliases
- oauth connection
- vercel oauth connection
- use oauth connection
- add oauth connection
- support oauth connection
- Evidence
- integrations.py OAuth and publishing.py Vercel project/deployment flow
- Limitation
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
vercelobservability
unsupported — Laygent v1 does not implement observability in its vercel target.
Requirements and limitations
- Id
- vercel.observability
- Status
- unsupported
- Aliases
- observability
- vercel observability
- use observability
- add observability
- support observability
- Evidence
- Limitation
- Laygent v1 does not implement observability in its vercel target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
vercelpreview creation
unsupported — Laygent v1 does not implement preview creation in its vercel target.
Requirements and limitations
- Id
- vercel.preview_creation
- Status
- unsupported
- Aliases
- preview creation
- vercel preview creation
- use preview creation
- add preview creation
- support preview creation
- Evidence
- Limitation
- Laygent v1 does not implement preview creation in its vercel target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
vercelpreview promotion
unsupported — Laygent v1 does not implement preview promotion in its vercel target.
Requirements and limitations
- Id
- vercel.preview_promotion
- Status
- unsupported
- Aliases
- preview promotion
- vercel preview promotion
- use preview promotion
- add preview promotion
- support preview promotion
- Evidence
- Limitation
- Laygent v1 does not implement preview promotion in its vercel target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
vercelproduction deployment
supported — Laygent v1 implements production deployment in its vercel target.
Requirements and limitations
- Id
- vercel.production_deployment
- Status
- supported
- Aliases
- deploy production
- go live
- vercel deployment
- publish website
- production deployment
- vercel production deployment
- use production deployment
- add production deployment
- support production deployment
- Evidence
- integrations.py OAuth and publishing.py Vercel project/deployment flow
- Limitation
- Required slots
- None
- Dependencies
- vercel.project_creation
- git.repository_creation
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
vercelproject creation
supported — Laygent v1 implements project creation in its vercel target.
Requirements and limitations
- Id
- vercel.project_creation
- Status
- supported
- Aliases
- project creation
- vercel project creation
- use project creation
- add project creation
- support project creation
- Evidence
- integrations.py OAuth and publishing.py Vercel project/deployment flow
- Limitation
- Dependencies
- None
- Conflicts
- None
- Defaults
- Project name
- laygent-app
- Clarify when
- None
- Alternatives
- None