You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
oc-build-deploy-dind was removed in #3110. However we still have parts of the documentation and codebase which refers to features that only existed in that build system.
All unsupported content which no longer has effect on Lagoon builds should be removed from across the documentation and codebase.
Screenshots
n/a
Additional context
To help users who have deprecated or unsupported fields in their .lagoon.yml, checks can be added to the deprecated profile in lagoon-linter so that eventually we can put warnings in the build log. Raise issues over there to add the required checks.
The text was updated successfully, but these errors were encountered:
Describe the bug
oc-build-deploy-dind
was removed in #3110. However we still have parts of the documentation and codebase which refers to features that only existed in that build system.Some examples:
lagoon.yml
additional-yaml
- Removed in update docs to remove Openshift references #3195, do we need to document/lint that it's deprecated?environments.[name].templates
hsts
- Support was added back, but the old config should be deprecatedmonitoring_urls
- Deprecate then Removemonitoring_urls
#2975hsts
should be removed from the templates.skip-on-kubernetes
should be removed since Lagoon no longer supports any other platform.To Reproduce
Steps to reproduce the behavior:
.lagoon.yml
documentation.monitoring_urls
.Expected behavior
All unsupported content which no longer has effect on Lagoon builds should be removed from across the documentation and codebase.
Screenshots
n/a
Additional context
To help users who have deprecated or unsupported fields in their
.lagoon.yml
, checks can be added to thedeprecated
profile inlagoon-linter
so that eventually we can put warnings in the build log. Raise issues over there to add the required checks.The text was updated successfully, but these errors were encountered: