cli

cli copied to clipboard

I'm seeing the following error when trying to update confluent locally on Apple M1 using macOS 13.3.1 (a) (Ventura):

➜ confluent update
Checking for updates...
New version of confluent is available
Current Version: v3.11.0
Latest Version:  v3.12.0
[5/4/2023] Confluent CLI v3.12.0 Release Notes
==============================================

New Features
------------
  - Add `--topics` flag to `confluent asyncapi export` to only export specified topics



Do you want to download and install this update? (y/n): y
Downloading confluent version 3.12.0...
Done. Downloaded 43.31 MB in 1 seconds. (32.41 MB/s)
Error: update client failure: error updating CLI binary: unable to copy /var/folders/0_/nkh8mcg92pq1fft8mrzcg98w0000gn/T/confluent3475877262/confluent-v3.12.0-darwin-arm64 to /usr/local/bin/confluent: remove /usr/local/bin/confluent: permission denied

Suggestions:
    Please submit a support ticket.
    In the meantime, see link for other ways to download the latest CLI version:
    https://docs.confluent.io/current/cli/installing.html

However, I'm not seeing the issue Intel macOS 11.7.6 (Big Sur):

➜ confluent update
Checking for updates...
New version of confluent is available
Current Version: v3.11.0
Latest Version:  v3.12.0
[5/4/2023] Confluent CLI v3.12.0 Release Notes
==============================================

New Features
------------
  - Add `--topics` flag to `confluent asyncapi export` to only export specified topics



Do you want to download and install this update? (y/n): y
Downloading confluent version 3.12.0...
Done. Downloaded 45.67 MB in 3 seconds. (14.25 MB/s)

In short, one needs do sudo confluent update instead confluent update. Thus, I believe that the confluent binary executable should invoke sudo in such situations.

Hi @conradwt, I haven't been able to replicate this even though I'm also using macOS 13.3.1 (a). Do you mind showing me the output of ls -l /usr/local/bin/confluent?

@brianstrauch Here's the output:

➜ ls -l /usr/local/bin/confluent
-rwxr-xr-x  1 root  wheel  45408592 May 12 18:33 /usr/local/bin/confluent

@conradwt we added a fix a while ago. can you confirm if you still see the issue? The latest cli version is v3.25.0

@MuweiHe I'm still seeing the following issue:

➜ confluent update                    
Checking for updates...
New version of confluent is available
Current Version: v3.24.0
Latest Version:  v3.25.0

[7/27/2023] Confluent CLI v3.25.0 Release Notes
===============================================

New Features
------------
- Add `confluent feedback` for user-submitted feedback
- When authenticated with Confluent Cloud, no longer require an API key for Schema Registry operations
- Add `confluent kafka cluster configuration` commands for managing dedicated cluster configurations

Bug Fixes
---------
- Correctly display Confluent Platform mirror topics in `confluent kafka link list --include-topics`
- Fix `confluent asyncapi import` and `confluent asyncapi export` to follow AsyncAPI documentation for Kafka channel bindings, with explicit fields for `bindingVersion`, `partitions`, and `topicConfiguration`
- Improve error message when no API secret is provided to `confluent kafka client-config create`

Do you want to download and install this update? (y/n): y
Downloading confluent version 3.25.0...
Done. Downloaded 49.74 MB in 2 seconds. (20.59 MB/s)
Error: update client failure: error updating CLI binary: open /usr/local/bin/.confluent.new: permission denied

Suggestions:
    Please submit a support ticket.
    In the meantime, see link for other ways to download the latest CLI version:
    https://docs.confluent.io/current/cli/installing.html

BTW, /usr/local/bin is write-protected in macOS 13.* (Ventura) and is owned by root. Thus, you'll need to invoke the command with sudo. Now, this will cause a minor issue making the file owned by root instead of $USER. BTW, on early versions of macOS like Big Sur, /usr/local/bin is owned by $USER and I can easily install updates using confluent update. Just something to be aware of while using the latest versions of macOS.

Thanks @conradwt, we're working on a fix! In the meantime, installing the CLI with Homebrew should fix this problem for anyone who runs into it in the future.

@brianstrauch I use MacPorts over here and it looks like there's a port available. Thus, I'll give that a spin.