Description:
Currently, on every PR we run a custom workflow to validate data files including landscape.yml, settings.yml, guide.yml using build command provided by the landscape tool for our CI/CD workflow. I suggest that we use the official validator action for the PR and then we can maintain our custom deploy logic separately. This way, we won't have to maintain the tool's data validation manually incase there are any breaking changes given this warning on the repo.
[!WARNING]
Landscape2 is at an early stage of development. There may be breaking changes in the future to the command usage, flags, and configuration file formats.
We could split our current workflow into two separate workflows, one workflow to validate all files including settings, guide, data yaml and another workflow to deploy to cloudflare.
Description: Currently, on every PR we run a custom workflow to validate data files including landscape.yml, settings.yml, guide.yml using build command provided by the landscape tool for our CI/CD workflow. I suggest that we use the official validator action for the PR and then we can maintain our custom deploy logic separately. This way, we won't have to maintain the tool's data validation manually incase there are any breaking changes given this warning on the repo.
Suggested Approach: