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

[hue] update action for July 2024 #1202

Merged
merged 3 commits into from
Jul 25, 2024

Conversation

cjac
Copy link
Contributor

@cjac cjac commented Jul 24, 2024

modified: hue/README.md

  • line-wrapped and clarified important note

modified: hue/hue.sh

  • added functions os_id, is_debian, is_debian10, is_ubuntu

  • only adding buster-backports to sources.list for debian10

  • update_repo now uses is_debian || is_ubuntu rather than checking for apt-get in path

  • setting DEBIAN_FRONTEND=noninteractive before installation of hue ; mysql-community-server had an important message that it was prompting the user to answer on a non-interactive console, halting tests.

  • added note that we may need to specify this option with debconf

  • jettisoned my function remove_old_backports with preference for Prince's much better replace_backports_repo

  • using slightly different logic to determine whether we replace the backports repo

modified:   hue/README.md

* line-wrapped and clarified important note

modified:   hue/hue.sh

* added functions os_id, is_debian, is_debian10, is_ubuntu
* only adding buster-backports to sources.list for debian10
* update_repo now uses is_debian || is_ubuntu rather than checking for
  apt-get in path
* setting DEBIAN_FRONTEND=noninteractive before installation of hue ;
  mysql-community-server had an important message that it was
  prompting the user to answer on a non-interactive console, halting
  tests.
* added note that we may need to specify this option with debconf

* jettisoned my function remove_old_backports with preference for
  Prince's much better replace_backports_repo

* using slightly different logic to determine whether we replace the
  backports repo
@cjac
Copy link
Contributor Author

cjac commented Jul 24, 2024

/gcbrun

@cjac
Copy link
Contributor Author

cjac commented Jul 24, 2024

/gcbrun

@cjac
Copy link
Contributor Author

cjac commented Jul 24, 2024

The previous run didn't seem to get the message that the installation was noninteractive and stopped again with the following prompt. I do not see this behavior in my reproduction environment.

Setting up mysql-community-server (8.0.39-1ubuntu20.04) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Configuring mysql-community-server
----------------------------------

MySQL 8 uses a new authentication based on improved SHA256-based password 
methods. It is recommended that all new MySQL Server installations use this 
method going forward. This new authentication plugin requires new versions of 
connectors and clients, with support for this new authentication method 
(caching_sha2_password). Currently MySQL 8 Connectors and community drivers 
built with libmysqlclient21 support this new method. Clients built with older 
versions of libmysqlclient may not be able to connect to the new server.

To retain compatibility with older client software, the default authentication 
plugin can be set to the legacy value (mysql_native_password) This should only 
be done if required third-party software has not been updated to work with the 
new authentication method. The change will be written to the file 
/etc/mysql/mysql.conf.d/default-auth-override.cnf

After installation, the default can be changed by setting the 
default_authentication_plugin server setting.

  1. Use Strong Password Encryption (RECOMMENDED)
  2. Use Legacy Authentication Method (Retain MySQL 5.x Compatibility)

Select default authentication plugin 

@cjac
Copy link
Contributor Author

cjac commented Jul 24, 2024

last test revealed that I had failed to define os_version on which is_debian depends. This should fix that last failure.

@cjac
Copy link
Contributor Author

cjac commented Jul 24, 2024

/gcbrun

@cjac cjac requested a review from prince-cs July 25, 2024 00:00
@cjac
Copy link
Contributor Author

cjac commented Jul 25, 2024

@prince-cs - this PR is ready for squash and merge. I believe i granted you authorization to perform reviews. Please review and approve if you believe we're ready to push this one out. I know that #1192 is blocked on hue and probably others.

@prince-cs prince-cs merged commit e8a4388 into GoogleCloudDataproc:master Jul 25, 2024
2 checks passed
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