Skip to content

Instantly share code, notes, and snippets.

@mlafeldt

mlafeldt/bug.md

Last active January 5, 2021 17:59
Show Gist options
  • Save mlafeldt/203a4aa45480d5dfa4fdb62fdf0a51a3 to your computer and use it in GitHub Desktop.
Save mlafeldt/203a4aa45480d5dfa4fdb62fdf0a51a3 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. mlafeldt revised this gist Jan 5, 2021. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion bug.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,6 @@
    ## Bug Report

    AWS Landing Zone version 2.4.1 is currently broken. More specifically, validation of manifest.yaml has been broken since Dec 30 when version 1.8.0 of https://pypi.org/project/pykwalify was released. This release requires schemas to be written in YAML 1.2. However, Landing Zone's current schema and manifest file adhere to YAML 1.1 (where `Yes|yes` still means `true`). The result is that the Build step of AWS-Landing-Zone-CodePipeline currently fails during schema validation.
    AWS Landing Zone version 2.4.1 is currently broken. More specifically, validation of manifest.yaml has been broken since Dec 30 when version 1.8.0 of https://pypi.org/project/pykwalify was released. This release requires schemas to be written in YAML 1.2. However, Landing Zone's current [schema](https://s3.amazonaws.com/solutions-reference/aws-landing-zone/latest/aws-landing-zone-validation.zip) and manifest file adhere to YAML 1.1 (where `Yes|yes` still means `true`). The result is that the Build step of AWS-Landing-Zone-CodePipeline currently fails during schema validation.

    ## Hotfix

  2. mlafeldt revised this gist Jan 5, 2021. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions bug.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,10 +1,10 @@
    ## Bug Report

    AWS Landing Zone version 2.4.1 is currently broken. More specifically, validation of manifest.yaml has been broken since Dec 30 when version 1.8.0 of https://pypi.org/project/pykwalify was released. This release requires schemas to be written in YAML 1.2. However, Landing Zone's current schema and manifest file adhere to YAML 1.1 (where `Yes|yes` still means `true`). The result is that the Build step currently fails during schema validation.
    AWS Landing Zone version 2.4.1 is currently broken. More specifically, validation of manifest.yaml has been broken since Dec 30 when version 1.8.0 of https://pypi.org/project/pykwalify was released. This release requires schemas to be written in YAML 1.2. However, Landing Zone's current schema and manifest file adhere to YAML 1.1 (where `Yes|yes` still means `true`). The result is that the Build step of AWS-Landing-Zone-CodePipeline currently fails during schema validation.

    ## Hotfix

    Update the Buildspec if AWS-Landing-Zone-CodeBuild:
    Update the buildspec of AWS-Landing-Zone-CodeBuild like this:

    ```diff
    - - pip install --upgrade pykwalify
  3. mlafeldt revised this gist Jan 5, 2021. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion bug.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,6 @@
    ## Bug Report

    AWS Landing Zone version 2.4.1 is currently broken. More specifically, validation of manifest.yaml has been broken since Dec 30 when version 1.8.0 of https://pypi.org/project/pykwalify was released. This release requires schema to be written in YAML 1.2. However, Landing Zone's current schema and manifest file adhere to YAML 1.1 (where `Yes|yes` is still means `true`). The result is that the Build step currently fails during schema validation.
    AWS Landing Zone version 2.4.1 is currently broken. More specifically, validation of manifest.yaml has been broken since Dec 30 when version 1.8.0 of https://pypi.org/project/pykwalify was released. This release requires schemas to be written in YAML 1.2. However, Landing Zone's current schema and manifest file adhere to YAML 1.1 (where `Yes|yes` still means `true`). The result is that the Build step currently fails during schema validation.

    ## Hotfix

  4. mlafeldt renamed this gist Jan 5, 2021. 1 changed file with 0 additions and 0 deletions.
    0 gistfile1.txt → bug.md
    View file
    File renamed without changes.
  5. mlafeldt created this gist Jan 5, 2021.
    14 changes: 14 additions & 0 deletions gistfile1.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,14 @@
    ## Bug Report

    AWS Landing Zone version 2.4.1 is currently broken. More specifically, validation of manifest.yaml has been broken since Dec 30 when version 1.8.0 of https://pypi.org/project/pykwalify was released. This release requires schema to be written in YAML 1.2. However, Landing Zone's current schema and manifest file adhere to YAML 1.1 (where `Yes|yes` is still means `true`). The result is that the Build step currently fails during schema validation.

    ## Hotfix

    Update the Buildspec if AWS-Landing-Zone-CodeBuild:

    ```diff
    - - pip install --upgrade pykwalify
    + - pip install --upgrade pykwalify==1.7.0 # HOTFIX for schema validation
    ```

    AWS should apply that fix to the initiation template or, better yet, update all affected files to YAML 1.2.