`steampipe plugin install aws` not working: `failed to resolve 0.144.0`
Describe the bug
Installation of the AWS plugin fails with error:
steampipe plugin install aws
aws [=====================>----------------------------------------------] Installing Plugin
Skipped the following plugin:
Plugin: [email protected]
Reason: failed to resolve 0.144.0: GET "https://ghcr.io/v2/turbot/steampipe/plugins/turbot/aws/manifests/0.144.0": GET "https://ghcr.io/token?scope=repository%3Aturbot%2Fsteampipe%2Fplugins%2Fturbot%2Faws%3Apull&service=ghcr.io": response status code 403: denied: denied
Steampipe version (steampipe -v)
Steampipe v0.23.2
To reproduce
brew install turbot/tap/steampipe
steampipe plugin install aws
Expected behavior
I would expect that the AWS plugin would be installed
Context
Running on MacOS Sanoma 14.5 - M1 chip
Workaround for this issue is to install the plugin locally.
$ cd ~/.steampipe/plugins
$ git clone https://github.com/turbot/steampipe-plugin-aws.git
$ cd steampipe-plugin-aws
$ git fetch --all --tags --prune
$ git checkout v0.144.0 -b v0.144.0
$ make
go build -o ~/.steampipe/plugins/hub.steampipe.io/plugins/turbot/aws@latest/steampipe-plugin-aws.plugin -tags "netgo" *.go
go: downloading github.com/aws/aws-sdk-go-v2 v1.27.0
go: downloading github.com/aws/aws-sdk-go-v2/credentials v1.17.16
go: downloading github.com/aws/aws-sdk-go-v2/config v1.27.16
go: downloading github.com/aws/aws-sdk-go-v2/feature/s3/manager v1.16.21
go: downloading github.com/aws/aws-sdk-go-v2/service/accessanalyzer v1.29.1
(...)
Configure the plugin:
cp config/* ~/.steampipe/config
vi ~/.steampipe/config/aws.spc
steampipe plugin list
+--------------------------------------------+---------+-------------+
| Installed | Version | Connections |
+--------------------------------------------+---------+-------------+
| hub.steampipe.io/plugins/turbot/aws@latest | local | aws |
+--------------------------------------------+---------+-------------+
Hey @egbertp apologies for this; we should have this fixed in the forthcoming 0.23.3 patch release.
@egbertp just wanted to check that this has been resolved for you in the latest update?
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
This issue was closed because it has been stalled for 90 days with no activity.