Deployment fails with YamlParseError #87
-
DescriptionAfter toggling an environment's activation switch, I got an error:
Files
---
components:
- name: WordPress
type: service
image: wordpress:6.4.1-php8.2-apache
port: 80
build: &buildwp
steps:
- directory: /usr/src/wordpress
- run: find /etc/apache2 -name '*.conf' -type f -exec sed -ri -e "s!/var/www/html!/usr/src/wordpress/web!g" -e "s!Directory /var/www/!Directory /usr/src/wordpress/web!g" '{}' +
- copy: bin/
- run: sh bin/install-composer.sh
- run: sh bin/install-wpcli.sh
- run: apt update && apt install -y jq
- copy: wp-cli.yml
- copy: composer.json
- copy: composer.lock
- run: composer install
- copy: config/
- copy: web/
runtime: &runtimewp
resources:
- MySQLDatabase
- S3Bucket
variables:
STACK_ID:
$stack: id
APP_NAME:
$app: name
WP_ENV:
$env:
if:
- var: production
- production
- development
AWS_REGION:
$env: region
DB_HOST:
$resources: MySQLDatabase.host
DB_NAME:
$resources: MySQLDatabase.database
DB_USER:
$resources: MySQLDatabase.username
DB_PASSWORD:
$resources: MySQLDatabase.password
S3_UPLOADS_BUCKET:
$resources: S3Bucket.bucket
S3_UPLOADS_ENDPOINT:
$resources: S3Bucket.endpoint
S3_UPLOADS_REGION:
$env: region
- name: WordPressCron
type: task
image: curlimages/curl:latest
cron: '* * * * *'
runtime:
command: curl --fail-with-body http://localstack/wp/wp-cron.php
- name: SaltGenerator
type: task
image: stedolan/jq:latest
build:
steps:
- copy: bin/salts.sh
destination: /tmp/salts.sh
runtime:
entrypoint: ''
command: sh /tmp/salts.sh
- name: WordPressInstaller
type: task
image: wordpress:6.4.1-php8.2-apache
build: *buildwp
runtime:
<<: *runtimewp
command: sh -c bin/install-wordpress.sh
entrypoint: ''
routes:
- target:
component: WordPress
resources:
- name: MySQLDatabase
type: mysql
- name: S3Bucket
type: s3 The repository (this is a different repo from https://github.com/orgs/noop-inc/discussions/85): |
Beta Was this translation helpful? Give feedback.
Answered by
derekwolpert
Jan 26, 2024
Replies: 1 comment
-
The |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
derekwolpert
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
YamlParseError
being encountered here is due to an invalid Runbook manifest file included in this repo's.noop
directory. Additional error handling will be included in the next release of Noop Desktop to make it easier to discern the cause of aYamlParseError
when encountered.