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

Bugfix 221 empty password #222

Merged
merged 5 commits into from
Aug 16, 2023
Merged

Bugfix 221 empty password #222

merged 5 commits into from
Aug 16, 2023

Conversation

bikegeek
Copy link
Collaborator

@bikegeek bikegeek commented Aug 7, 2023

Pull Request Testing

  • Describe testing already performed for these changes:

    Passes the Github workflow tests for METreformat, which use the code (but not the db loading aspect)

testing done on code in the bugfix_221_empty_password branch

  • Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:

    verify this works on an AWS instance using the bugfix_221_empty_password branch

  • Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [NA]

  • Do these changes include sufficient testing updates? [NA]

  • Will this PR result in changes to the test suite? [No]

    If yes, describe the new output and/or changes to the existing output:

  • Please complete this pull request review by At earliest convenience, since this is a blocker.

Pull Request Checklist

See the METplus Workflow for details.

  • Add any new Python packages to the METplus Components Python Requirements table.
  • Review the source issue metadata (required labels, projects, and milestone).
  • Complete the PR definition above.
  • Ensure the PR title matches the feature or bugfix branch name.
  • Define the PR metadata, as permissions allow.
    Select: Reviewer(s)
    Select: Organization level software support Project or Repository level development cycle Project
    Select: Milestone as the version that will include these changes
  • After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
  • After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
  • Close the linked issue and delete your feature or bugfix branch from GitHub.

…rd is missing. This allows cloud-users to continue without a password.
…ord.

If the username is missing, continue to log an error and raise a NameError.
However, if the password is missing, log a warning and continue, to support cloud-based
instances.
@TatianaBurek
Copy link
Collaborator

I successfully tested the new code.
I asked Binbin to do a complete test from WCOSS

raise NameError("Missing required user or password tag or both")

if not self.connection['db_user']:
logging.warning("!!! XML expecting user and password tags")
Copy link
Collaborator

Choose a reason for hiding this comment

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

The warning message still contains word "password"

@bikegeek
Copy link
Collaborator Author

bikegeek commented Aug 7, 2023 via email

@TatianaBurek TatianaBurek linked an issue Aug 7, 2023 that may be closed by this pull request
23 tasks
@bikegeek bikegeek merged commit 24ddbcb into main_v2.1 Aug 16, 2023
14 checks passed
@bikegeek bikegeek deleted the bugfix_221_empty_password branch August 16, 2023 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

Password field in loading XML files can be empty
2 participants