-
Notifications
You must be signed in to change notification settings - Fork 31
File specific scenarios for aio runtime deploy commands
aio runtime deploy command requires a flag specifying the manifest string which indicates the path to the manifest file.
Example:
aio runtime deploy --manifest Desktop/manifest.yaml or aio runtime deploy -m Desktop/manifest.yml
The path to the manifest file is mandatory for aio runtime deploy to work.
If this flag is not passed with the command, the aio cli looks for a file called manifest.yaml in the current working directory. If manifest.yaml is found, it is used as the manifest file to deploy from . However, if manifest.yaml is not present, the aio cli looks for manifest.yml which, if found, serves as the manifest file for deployment. If none of these files are present in the current directory and a manifest string has not been passed as a flag, the aio runtime deploy command returns an error : Failed to deploy: Manifest file not found
aio runtime deploy command requires a flag specifying the deployment string which indicates the path to the deployment file.
Example:
aio runtime deploy --deployment Desktop/deployment.yaml or aio runtime deploy --deployment Desktop/deployment.yml
The path to the deployment file is NOT mandatory for aio runtime deploy to work.
If this flag is not passed with the command, the aio cli looks for a file called deployment.yaml in the current working directory. If deployment.yaml is found, it is used as the deployment file to bind parameters from. However, if deployment.yaml is not present, the aio cli looks for deployment.yml which, if found, serves as the deployment file for deployment. If none of these files are present in the current directory and a deployment string has not been passed as a flag, the aio runtime deploy ignores the usage of deployment file for binding parameters
The report, undeploy and report subcommands of aio runtime deploy work with the manifest and deployment files in a similar way as explained above.