-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CDS-105745] Added note related to undefined variables in expressions… #9077
Conversation
… in NG pipeline In Harness NG pipelines, undefined variables in expressions will cause a pipeline execution error. Unlike FirstGen pipelines, where undefined variables default to `null`, NG requires explicit handling of undefined variables.
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://678801680c18801abb7acea1--harness-developer.netlify.app |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment, otherwise LGTM, but I'm not a codeowner, so this PR won't merge.
@@ -217,6 +217,12 @@ Additionally, variable values (after evaluation) are limited to 256 KB. Expressi | |||
|
|||
::: | |||
|
|||
:::note | |||
|
|||
In Harness NG pipelines, undefined variables in expressions will cause a pipeline execution error. Unlike FirstGen pipelines, where undefined variables default to `null`, NG requires explicit handling of undefined variables. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In Harness NG pipelines, undefined variables in expressions will cause a pipeline execution error. Unlike FirstGen pipelines, where undefined variables default to `null`, NG requires explicit handling of undefined variables. | |
In Harness NG pipelines, undefined variables in expressions will cause a pipeline execution error unlike FirstGen pipelines, where undefined variables default to `null`. NG requires explicit handling of undefined variables. |
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://678899e6c8572df28fe5440a--harness-developer.netlify.app |
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://67889daec8572df66fe540e4--harness-developer.netlify.app |
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6788af44ab861c404b5260cd--harness-developer.netlify.app |
… in NG pipeline
In Harness NG pipelines, undefined variables in expressions will cause a pipeline execution error. Unlike FirstGen pipelines, where undefined variables default to
null
, NG requires explicit handling of undefined variables.Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: