Package Details: aws-session-manager-plugin

Git Clone URL: (read-only, click to copy)
Package Base: aws-session-manager-plugin
Description: AWS Session Manager Plugin for aws-cli.
Upstream URL:
Keywords: aws aws-cli plugin session-manager
Licenses: custom
Submitter: CallumDenby
Maintainer: CallumDenby
Last Packager: CallumDenby
Votes: 3
Popularity: 0.72
First Submitted: 2019-09-17 12:47
Last Updated: 2019-11-26 20:05

Latest Comments

1 2 Next › Last »

crou commented on 2019-11-22 02:30

@troyengel you are right, /opt is a much better location! I vote for it :-)

troyengel commented on 2019-11-21 20:07

@crou I was thinking about that overnight as well, I think /opt would be a more LFHS standard / compliant path to use rather than /usr/local (spec)- Amazon is our vendor and delivering a binary payload, which matches the general concept of other vendor tooling we have in AUR (google-cloud-sdk, Zoom, etc.) and how it's delivered to users.

crou commented on 2019-11-21 18:59

I haven't realized before, but is that expected to have this binary installed in /usr/sessionmanagerplugin/ ? /usr/local/sessionmanagerplugin would be more appropriate ;-)

troyengel commented on 2019-11-20 21:59

@CallumDenby I emailed you, easier to chat re: the versions. Not sure myself. :-/

troyengel commented on 2019-11-20 21:51

For anyone upgrading - because we just moved a non-package-tracked symlink into the package proper, you may see this when you attempt to upgrade to or above from an older version:

(1/1) checking for file conflicts                                                 [###############################################] 100%
error: failed to commit transaction (conflicting files)
aws-session-manager-plugin: /usr/bin/session-manager-plugin exists in filesystem

Just do a quick sudo rm /usr/bin/session-manager-plugin first then upgrade the package. Standard pacman behaviour, protecting you from possibly making a mistake.

CallumDenby commented on 2019-11-20 21:48

I found the same thing, I'm unsure whether to provide version 1.1.50 without it being documented within the web page. What do you advise?

troyengel commented on 2019-11-20 21:47

@CallumDenby I dug into the SHAs a bit, I think we're seeing a new version at the "latest" link which is not yet updated on the HTML page. After extracting the two payloads:

diff -uNr numbered/control/control latest/control/control
--- numbered/control/control    2019-10-11 17:28:21.000000000 -0500
+++ latest/control/control  2019-11-13 17:17:27.000000000 -0600
@@ -1,6 +1,6 @@
 Package: session-manager-plugin
 Architecture: amd64

(and other diffs saying the files don't match). Looks like a new is what "latest" actually is, not shrug

CallumDenby commented on 2019-11-20 21:45

/etc/init has now been removed, as has aws-session-manager-plugin.install

symlink is done within the package section in the PKGBUILD

CallumDenby commented on 2019-11-20 21:16

@troyengel checksums were updated, but it seems the links below have different checksums which I didn't check. Now updated. Going to add the other suggestions you made now.

troyengel commented on 2019-11-20 21:05

Also, I'm the one who just flagged it out of date - I think you updated the version, but did not update the SHA/checksum as I get an error now.

$ pikaur -S aws-session-manager-plugin


:: AUR package will be installed:
 aws-session-manager-plugin             ->


==> Retrieving sources...
  -> Downloading session-manager-plugin.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 3940k  100 3940k    0     0  4759k      0 --:--:-- --:--:-- --:--:-- 4753k
==> Validating source_x86_64 files with sha512sums...
    session-manager-plugin.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!