How to Install and Uninstall golang-github-googlecloudplatform-cloudsql-proxy.x86_64 Package on Fedora 39

Last updated: October 14,2024

1. Install "golang-github-googlecloudplatform-cloudsql-proxy.x86_64" package

Please follow the guidelines below to install golang-github-googlecloudplatform-cloudsql-proxy.x86_64 on Fedora 39


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                golang-github-googlecloudplatform-cloudsql-proxy.x86_64
            
                    
    
    Copied

2. Uninstall "golang-github-googlecloudplatform-cloudsql-proxy.x86_64" package

This guide let you learn how to uninstall golang-github-googlecloudplatform-cloudsql-proxy.x86_64 on Fedora 39:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                golang-github-googlecloudplatform-cloudsql-proxy.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the golang-github-googlecloudplatform-cloudsql-proxy.x86_64 package on Fedora 39

Last metadata expiration check: 3:18:54 ago on Thu Mar 7 17:44:52 2024.
Available Packages
Name : golang-github-googlecloudplatform-cloudsql-proxy
Version : 1.31.2
Release : 3.fc39
Architecture : x86_64
Size : 4.2 M
Source : golang-github-googlecloudplatform-cloudsql-proxy-1.31.2-3.fc39.src.rpm
Repository : fedora
Summary : Cloud SQL proxy client and Go library
URL : https://github.com/GoogleCloudPlatform/cloudsql-proxy
License : Apache-2.0
Description : The Cloud SQL Proxy allows a user with the appropriate permissions to connect
: to a Second Generation Cloud SQL database without having to deal with IP
: whitelisting or SSL certificates manually. It works by opening unix/tcp
: sockets on the local machine and proxying connections to the associated
: Cloud SQL instances when the sockets are used.