support object initializeCommand (#12)

* try removing current workaround

* will runCmd let action use devcontainer up?

* how about this

* oh

* fix

.github/workflows/update-devcontainer.yml

@@ -27,20 +27,17 @@ jobs:
           username: ${{ github.actor }}
           password: ${{ github.token }}
 
-      - name: run initializeCommand
-        # temporary workaround. See https://github.com/devcontainers/cli/issues/190
+      - name: actual build
+        # use devcontainer up instead of devcontainer build. See https://github.com/devcontainers/cli/issues/190
         run: |
+          set -e
+
           npm install -g @devcontainers/cli
-          
-          initializeCommand=`devcontainer read-configuration --workspace-folder "${{ inputs.directory }}" | jq --raw-output .configuration.initializeCommand`
-          if [[ $initializeCommand != 'null' ]]; then
-            echo "about to execute $initializeCommand"
-            eval "$initializeCommand"
-          fi
+          devcontainer up --workspace-folder ${{ inputs.directory }} --prebuild --build-no-cache --skip-post-create
 
-      - uses: devcontainers/ci@c3e31cc561800ac318ed000e22ffc6713c93d009
+      - name: upload image
+        uses: devcontainers/ci@c3e31cc561800ac318ed000e22ffc6713c93d009
         with:
           imageName: ${{ inputs.image-name }}
           subFolder: ${{ inputs.directory }}
           push: ${{ inputs.push }}
-          noCache: true