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

User domain name to domain name #596

Merged
merged 1 commit into from
Jul 21, 2023

Conversation

yaacov
Copy link
Member

@yaacov yaacov commented Jul 21, 2023

Ref: #591

Issue:
When creating an OpenStack provider with Token with User Name authentication type, the domainName/domainId is needed in the secret, while the userDomainName is not a must.
Currently, there is no Domain Name filed on creating provider page, the provider will be in connectonfailed status. Need to change the User Domain Name field to Domain Name

Screenshot:

screenshot-localhost_9000-2023 07 21-17_01_14(1)

@yaacov yaacov added the bug Categorizes issue or PR as related to a bug. label Jul 21, 2023
@yaacov yaacov added this to the 2.5.0 milestone Jul 21, 2023
@yaacov yaacov force-pushed the user-domain-name-to-domain-name branch from b84b464 to e7ad1b2 Compare July 21, 2023 14:12
@sonarcloud
Copy link

sonarcloud bot commented Jul 21, 2023

SonarCloud Quality Gate failed.    Quality Gate failed

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

No Coverage information No Coverage information
55.0% 55.0% Duplication

idea Catch issues before they fail your Quality Gate with our IDE extension sonarlint SonarLint

@@ -42,9 +42,6 @@ export const openstackSecretFieldValidator = (id: string, value: string) => {
case 'projectID':
validationState = validateProjectID(trimmedValue) ? 'success' : 'error';
break;
case 'userDomainName':
validationState = validateUserDomainName(trimmedValue) ? 'success' : 'error';
break;
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't the domainName be validated? I see you dropped userDomainName validation but you didn't add the equivalent for domainName...

Copy link
Member Author

Choose a reason for hiding this comment

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use domainName instead of userDomainName when Token with User Name authentication type is selected
2 participants