Disabling Lightspeed in settings does not disable features

[timfallmk]

Summary

With the introduction of new Lightspeed integration in 2.0 I'm now getting bugged to "log in to ansible lightspeed to use ansible" on every open window. I have the "Lightspeed" enable option unchecked in the settings.

There may be other parts of Lightspeed that are not being disabled when the user explicitly does not enable them.

Extension version

v2.0.58

VS Code version

1.77.3

Ansible Version

ansible [core 2.14.4]
  config file = /Users/tfall/Code/stand-configuration/ansible.cfg
  configured module search path = ['/Users/tfall/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/homebrew/Cellar/ansible/7.4.0/libexec/lib/python3.11/site-packages/ansible
  ansible collection location = /Users/tfall/.ansible/collections:/usr/share/ansible/collections
  executable location = /opt/homebrew/bin/ansible
  python version = 3.11.3 (main, Apr  7 2023, 20:13:31) [Clang 14.0.0 (clang-1400.0.29.202)] (/opt/homebrew/Cellar/ansible/7.4.0/libexec/bin/python3.11)
  jinja version = 3.1.2
  libyaml = True

OS / Environment

macOS Ventura 13.3.1
ansible-lint 6.14.6 using ansible 2.14.4

Relevant log output

No response

[rothfralick]

Same here. Very annoying.
Ansible extension v2.0.58
VSCode 1.77.3
Windows 11

[Zombiefleischer]

Also autocompletion is not working with this new version
Ansible extension v2.0.58
VSCode 1.77.3
Linux Debian

[harwinds]

Same here, please give me the option to disable it. Get rid of the (1) indicator.

[ganeshrn]

@timfallmk Thanks for raising the issue, we will work on the fix.

@Zombiefleischer

Also autocompletion is not working with this new version

Autocompletion should work irrespective of Lightspeed is enabled or disabled.
Is it possible for you to share a screen recording?
Also the debug logs, you can refer this to get the debug logs

[Zombiefleischer]

I went back to v1.2.44 for the time being and to get the screen recording I switched back to the latest version (v2.0.58) and it automagically fixed itself. I don't know what went wrong, but it works fine now. Sorry for the inconvenience.

[lcrownover]

I assume based on response that this is a known issue that will be resolved, but I figured I'd just add to the dogpile.

That (1) is annoying!

[rubin55]

The message is:

Sign in with Ansible Lightspeed to use Ansible(1)

Question: Is the intention of this to communicate the Ansible extension won't work unless you log in using Ansible Lightspeed?

[ganeshrn]

@rubin55 Ansible extension will continue to work irrespective of user has logged in to the Ansible Lightspeed service. I agree the message is misleading and we can change it.

Ansible Lightspeed is currently in closed beta and provides AI based code suggestion and for this feature to work users will have to log in to the Lightspeed service.

[safderali5]

very annoying and no way to disable this :-(

[harwinds]

I actually unchecked the Accounts from the side bar to get rid of the annoying (1) for the Ansible extension.

[MrSteve81]

Also autocompletion is not working with this new version Ansible extension v2.0.58 VSCode 1.77.3 Linux Debian

I can also confirm when i am on v2.0.58 the auto complete for modules does not work

but when i switch back to Ansible
v1.2.44 it works

[ganeshrn]

The notification disable issue is fixed by PR #877 and will be available in the next minor version release of the extension.
Unfortunately there is no direct way provided by VSCode API's to change the sign in message as reported in the comment #859 (comment). We have raised a new issue #879 to track it and it might take some time to fix it.

[ganeshrn]

@MrSteve81 The autocompletion feature should work irrespective of if you sign to Lightspeed service or not. Please refer to my comment #859 (comment). After updating the version try reloading VSCode. It might be an intermittent issue as reported here #859 (comment)

[dszryan]

"ansible.lightspeed.URL": "",

seemed to have reduced the annoyance

[huyz]

"ansible.lightspeed.URL": "",

hehe that's the kind of workaround that will make it harder to adopt this new feature when it is actually available—perhaps devs will learn from that for next time.

[mousedownmike]

Setting "ansible.lightspeed.URL": "", didn't remove the Sign In badge for me on Linux and MacOS. It looked like it did when I first made the change, but the badge came back after subsequent reloads.