Commands & OpenAPI
Run alias commands and generate API descriptions in the alias context.
Command definitions
Alias command definitions must identify the alias application. Command implementations can still come from origin classes. Ensure command names and alternative aliases are unique and that the correct application context is selected.
OpenAPI generation
Generate the OpenAPI specification under the alias application identity. The resulting API description must use the alias routes and server addresses while allowing the origin implementation classes to be loaded.
REST verification
Test alias endpoints independently, including bearer security and CORS. A successful specification build is not proof that all data accesses are isolated.
Configuration and command examples
These examples are preserved from the alias pre-documentation. Review the active environment and application names before applying them.
'commands' => [
'alias-dns:configuration:validate' => [
'name' => 'alias-dns:configuration:validate',
'class' => 'AppnetosDnsControl\\Command\\ValidateConfiguration',
'description' => 'Generates and validates the complete BIND configuration',
'aliases' => [],
'active' => true,
'hidden' => false,
],
],
php bin/appnetos cmd appnetos:cmd:list --all
php bin/appnetos cmd alias-appnetos-dns-control alias-dns:configuration:validate
php bin/appnetos cmd appnetos:cmd:generate alias-appnetos-dns-control
php bin/appnetos cmd appnetos:openapi:generate alias-appnetos-dns-control
curl -i 'http://localhost:20002/rest/admin-app?limit=25&page=1&direction=asc' -H 'Accept: application/json'
curl -i -X OPTIONS 'http://localhost:20002/rest/admin-app' -H 'Origin: http://localhost:20000' -H 'Access-Control-Request-Method: GET' -H 'Access-Control-Request-Headers: authorization'