Skip to content

Conversation

stepansergeevitch
Copy link
Collaborator

Fixed missing errors for invalid account_name for ResourceManager and connect

@stepansergeevitch stepansergeevitch self-assigned this Jun 6, 2022
@stepansergeevitch stepansergeevitch changed the title Fir 11539 setting non existing account n fix: Fir 11539 setting non existing account n Jun 6, 2022
Comment on lines 225 to 227
elif account_name:
# We need to manually validate account_name since it's not validated
# in neither of above cases
Copy link
Contributor

Choose a reason for hiding this comment

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

Should it be if instead? So if above cases pass it still validates the account name?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Account name gets validated in those cases since it's used to get/resolve engine url.
I'll extend a comment explaining that

@stepansergeevitch stepansergeevitch force-pushed the FIR-11539-setting-non-existing-account_n branch from cb3b4bb to 4320c98 Compare June 6, 2022 13:25
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jun 6, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@stepansergeevitch stepansergeevitch merged commit 0779fdf into main Jun 6, 2022
@stepansergeevitch stepansergeevitch deleted the FIR-11539-setting-non-existing-account_n branch June 6, 2022 14:38
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.

2 participants