Package Details: pulumi-bin 2.5.0-1

Git Clone URL: https://aur.archlinux.org/pulumi-bin.git (read-only, click to copy)
Package Base: pulumi-bin
Description: Modern Infrastructure as Code
Upstream URL: https://github.com/pulumi/pulumi
Keywords: aws azure gcp iac infrastructure
Licenses: Apache-2.0
Submitter: subosito
Maintainer: farnoy (hnicke, sudoforge)
Last Packager: hnicke
Votes: 4
Popularity: 0.066414
First Submitted: 2018-07-24 10:30
Last Updated: 2020-06-25 20:47

Dependencies (0)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

pluppens commented on 2020-03-31 09:33

@sudoforge: thank you, again! I removed the old build directory, and now it works.

For anyone else using the package manager and struggling to find where to find the old build sources: remove the pulumi-bin directory from /var/tmp/pamac-build-{USER}/ where {USER} will be your username.

After that, the build will work just fine.

sudoforge commented on 2020-03-31 09:04

@pluppens:

That being said - there's also the pulumi package - since both seem to be at the same release, it's hard to know which one to pick for complete newcomers such as myself.

In the AUR, by convention (and not by rule):

  • *-bin packages are prebuilt binaries, so you don't need to compile the executable yourself
  • *-git packages will fetch the latest HEAD of the project and compile the executable each time they are built
  • Non *-bin and *-git packages track the latest versioned release of a project, and require compiling the executable yourself.

pluppens commented on 2020-03-30 20:57

@sudoforge: much obliged! I'll have a look to see how I can clean the build cache (I was using the Manjaro Package Manager), but I was under the impression every build should have started from a clean sheet.

That being said - there's also the pulumi package - since both seem to be at the same release, it's hard to know which one to pick for complete newcomers such as myself.

sudoforge commented on 2020-03-30 20:53

@pluppens, it looks like (based on the output you pasted) that you didn't clean your build cache, meaning that you fetched an updated PKGBUILD with a new checksum, and are using the old artifact (with the old checksum).

If you're using makepkg directly, use the --cleanbuild flag to clean $srcdir to fix the issue now, and build with --clean for future builds:

    -c, --clean
    Clean up leftover work files and directories after a successful build.

    -C, --cleanbuild
    Remove the $srcdir before building the package.

The checksum change was caused due to the fact that the Pulumi team changed the artifact after initial upload. I opened an issue about this 1, but don't really expect them to reply. If this happens often, I can implement a workaround that will offer more consistent builds, but in an ideal world this wouldn't be necessary.

pluppens commented on 2020-03-30 09:25

Hey folks, I'm getting a checksum failure on the 1.13.0-2 (I had 1.13.0-1 installed earlier):

Building pulumi-bin...
==> Making package: pulumi-bin 1.13.0-2 (Mon 30 Mar 2020 12:24:01 PM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found pulumi-v1.13.0-linux-x64.tar.gz
==> Validating source files with sha256sums...
    pulumi-v1.13.0-linux-x64.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Failed to build pulumi-bin

sudoforge commented on 2020-03-12 15:11

Hey folks, please make sure you reset the pkgrel to 1 when updating the pkgver.

sudoforge commented on 2020-02-27 23:27

@farnoy No worries; I'm usually able to update packages fairly immediately after upstream releases, and am happy to help.

farnoy commented on 2020-02-27 22:52

@sudoforge I've added you as co-maintainer, thanks for the help. I try to synchronize updates in my project with my dev machine, and since they release new versions so often, I failed to keep up :D

Good luck with your migration from Terraform :)

sudoforge commented on 2020-02-27 22:00

It'd be awesome if we could add the completion scripts to the system-level directories for {bash,zsh} with this package. Here's a patch that will do that:

diff --git a/.SRCINFO b/.SRCINFO
index fd51cac..a755b52 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,7 +1,7 @@
 pkgbase = pulumi-bin
    pkgdesc = A multi-language, multi-cloud development platform
    pkgver = 1.11.1
-   pkgrel = 1
+   pkgrel = 2
    url = https://github.com/pulumi/pulumi
    arch = x86_64
    license = Apache-2.0
diff --git a/PKGBUILD b/PKGBUILD
index 28d893e..47d34f1 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@
 pkgname=pulumi-bin
 _pkgname=pulumi
 pkgver=1.11.1
-pkgrel=1
+pkgrel=2
 pkgdesc="A multi-language, multi-cloud development platform"
 arch=('x86_64')
 license=('Apache-2.0')
@@ -20,4 +20,14 @@ package() {
   install -m755 "${srcdir}/${_pkgname}/${_pkgname}-language-python" "${pkgdir}/usr/bin/${_pkgname}-language-python"
   install -m755 "${srcdir}/${_pkgname}/${_pkgname}-language-python-exec" "${pkgdir}/usr/bin/${_pkgname}-language-python-exec"
   install -m755 "${srcdir}/${_pkgname}/${_pkgname}-resource-pulumi-nodejs" "${pkgdir}/usr/bin/${_pkgname}-resource-pulumi-nodejs"
+
+  # Generate Bash completion
+  mkdir -p "${pkgdir}/etc/bash_completion.d"
+  "${pkgdir}/usr/bin/${_pkgname}" gen-completion bash |\
+    install -m644 /dev/stdin "${pkgdir}/etc/bash_completion.d/${_pkgname}"
+
+  # Generate ZSH completion
+  mkdir -p "${pkgdir}/usr/local/share/zsh/site-functions"
+  "${pkgdir}/usr/bin/${_pkgname}" gen-completion zsh |\
+    install -m644 /dev/stdin "${pkgdir}/usr/local/share/zsh/site-functions/_${_pkgname}"
 }

If you copy the above to your clipboard, you can apply it by cd'ing to the same directory as the PKGBUILD and running patch -p1 <<(xclip -sel c -o). This will make changes to the files, but won't create a commit.

lietzu commented on 2019-07-01 19:03

@farnoy Thank you for updating this. I'm glad someone is giving this package the attention it deserves.