Skip to content
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

NIFI-13119: When evaluating dependent Properties, the UI should identify when the Property value is a parameter reference and resolve the value accordingly #8724

Merged
merged 4 commits into from
May 3, 2024

Conversation

mcgilman
Copy link
Contributor

@mcgilman mcgilman commented May 1, 2024

NIFI-13119:

  • When evaluating dependent Properties, the UI should identify when the Property value is a parameter reference and resolve the value accordingly.

@mcgilman mcgilman added the new ui Pull requests for work relating to the new user interface being developed. label May 1, 2024
@rfellows
Copy link
Contributor

rfellows commented May 2, 2024

reviewing

if (dependentItem.descriptor.sensitive) {
return true;
}

// if the dependent item is visible, but does not require a specific
// dependent value consider the dependency met
if (this.nifiCommon.isEmpty(dependency.dependentValues)) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to handle the scenario where the dependentItem.value is null so the dependency is not shown. An example of this is the AWSCredentialsProviderControllerService and the Assume Role ARN property. If it is unset, the other properties below it should not be shown (like Assume Role Session Name among others).

mcgilman added 3 commits May 2, 2024 15:46
- When evaluating dependent Properties, the UI should identify when the Property value is a parameter reference and resolve the value accordingly.
- Requiring a value to be present when showing dependent property that doesn't require any specific value.
- Using error helper to get error string.
- Handle convert to parameter error scenario.
Copy link
Contributor

@rfellows rfellows left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work, @mcgilman. I'll merge after CI completes.

@rfellows rfellows merged commit 160c7ae into apache:main May 3, 2024
5 checks passed
shubhluck pushed a commit to shubhluck/nifi that referenced this pull request Jun 1, 2024
…ify when the Property value is a parameter reference and resolve the value accordingly (apache#8724)

* NIFI-13119:
- When evaluating dependent Properties, the UI should identify when the Property value is a parameter reference and resolve the value accordingly.

* NIFI-13119:
- Requiring a value to be present when showing dependent property that doesn't require any specific value.

* NIFI-13119:
- Using error helper to get error string.

* NIFI-13119:
- Handle convert to parameter error scenario.

This closes apache#8724
shubhluck pushed a commit to shubhluck/nifi that referenced this pull request Jun 1, 2024
…ify when the Property value is a parameter reference and resolve the value accordingly (apache#8724)

* NIFI-13119:
- When evaluating dependent Properties, the UI should identify when the Property value is a parameter reference and resolve the value accordingly.

* NIFI-13119:
- Requiring a value to be present when showing dependent property that doesn't require any specific value.

* NIFI-13119:
- Using error helper to get error string.

* NIFI-13119:
- Handle convert to parameter error scenario.

This closes apache#8724
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new ui Pull requests for work relating to the new user interface being developed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants