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

RUN-2450: fix config for detectFirstrun #9118

Merged
merged 4 commits into from
May 17, 2024
Merged

RUN-2450: fix config for detectFirstrun #9118

merged 4 commits into from
May 17, 2024

Conversation

gschueler
Copy link
Member

Is this a bugfix, or an enhancement? Please describe.

Fixes the rundeck.startup.detectFirstRun config flag to work, enables setting it via remco.

Describe the solution you've implemented

Describe alternatives you've considered

Additional context

@gschueler gschueler added this to the 5.4.0 milestone May 13, 2024
@gschueler gschueler changed the title Run 2450 RUN-2450: fix config for detectFirstrun May 13, 2024
Copy link
Contributor

@mrdubr mrdubr left a comment

Choose a reason for hiding this comment

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

LGTM.
See the comment for a minor suggestion.
Verified with PAAP. Deferring RBA testing.

boolean shouldShowFirstRunInfo(){
boolean isFirstRun = false
if(configurationService.getBoolean(MenuService.SYS_CONFIG_DETECT_FIRST_RUN, true) &&
frameworkService.rundeckFramework.getPropertyLookup().hasProperty('framework.var.dir')) {
Copy link
Contributor

Choose a reason for hiding this comment

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

woah... one busy method! :-)

Would it make sense to synchronize this method given that it may result in a race condition when two requests are made to the controller endpoint?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think it's not necessary, if the race causes two or more requests to think the file doesn't exist, then worst case is that multiple users see the splash screen

Copy link
Member Author

Choose a reason for hiding this comment

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

arguably, this splash screen mechanism isn't very good because only 1 user would normally see it anyway.

@gschueler gschueler enabled auto-merge May 17, 2024 20:16
@gschueler gschueler merged commit e36904a into main May 17, 2024
4 checks passed
@gschueler gschueler deleted the RUN-2450 branch May 17, 2024 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants