Summary
When running cnspec scan --help, the Atlassian provider (atlassian) is not listed among the available subcommands, even though it works correctly once auto-installed. Other dynamically-installed providers like bigip, unifi, tailscale, mcp, shodan, snowflake, and cloudflare are listed in help output, but atlassian is missing.
Current behavior
$ cnspec scan --help
Available Commands:
arista Scan an Arista EOS device
aws Scan an AWS account
...
(no atlassian entry)
Running cnspec scan atlassian jira ... works — it auto-installs the provider and scans successfully — but there's no discoverability from the help text.
Expected behavior
atlassian should appear in the Available Commands list for cnspec scan, cnspec shell, and cnspec run, consistent with other providers.
Impact
Users and docs authors have no way to discover the Atlassian integration from the CLI help. The docs currently include a Jira scan example, but it's not obvious from the CLI that this is a supported target.
Summary
When running
cnspec scan --help, the Atlassian provider (atlassian) is not listed among the available subcommands, even though it works correctly once auto-installed. Other dynamically-installed providers likebigip,unifi,tailscale,mcp,shodan,snowflake, andcloudflareare listed in help output, butatlassianis missing.Current behavior
Running
cnspec scan atlassian jira ...works — it auto-installs the provider and scans successfully — but there's no discoverability from the help text.Expected behavior
atlassianshould appear in theAvailable Commandslist forcnspec scan,cnspec shell, andcnspec run, consistent with other providers.Impact
Users and docs authors have no way to discover the Atlassian integration from the CLI help. The docs currently include a Jira scan example, but it's not obvious from the CLI that this is a supported target.