Repository navigation
Document capture of Outputs and sls info results #26
Description
Activity
Solid tip
I made a plugin that outputs Outputs into a "manifest file" https://www.npmjs.com/package/serverless-manifest-plugin
This might help avoid some hardcore greps.
I'd love if
sls deployhad a--jsonflag to output a simple structure to parse withjq@DavidWells thanks, and nice plugin. I think we've identified the same need. The first time I saw you could set output params. this way in sls I thought it was great. When I found the only way to access them was re-running sls, requiring re-authorization and again setting the stage and the verbose flag, then having to dig for the result, I was not pleased.
Thank you @matthewpoer
Just want to add that I'm using
v2.18.0and had to change the shell to/bin/sh.Reacted by Matthew PoerThank you so much for this plugin!!!
My github workflow looks like this, and worked fine!deploy-backend: needs: build runs-on: ubuntu-latest environment: name: aws url: ${{ steps.manifest.outputs.url }} steps: - uses: actions/checkout@v2 - name: Download artifacts uses: actions/download-artifact@v2 with: name: jar-artifacts path: app/target - name: Install Plugin and Deploy uses: serverless/github-action@v3.2 with: args: -c "serverless plugin install --name serverless-manifest-plugin && serverless deploy --stage prd" entrypoint: /bin/sh env: AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }} - name: manifest id: manifest run: | url=$(cat .serverless/manifest.json | jq -r '.prd.urls.apiGateway') echo "::set-output name=url::$url" - run: echo ${{ steps.manifest.outputs.url }}
This took a while to figure out so I'd like to share and advise that it'd be nice to see in the README or elsewhere in the documentation.
My use case was that I needed to capture some of my
resources.Outputsfrom a serverless deployment for use with later scripting. For example, here's an excerpt from myserverless.ymlfile:With that in place I can run
sls info --verboseand capture in that output is the desiredPublicDnsNamebut I have to grep and adjust for that, e.g.All that said, I found it difficult to perform that scrub-and-grab sequence in a Github Action using this container, but finally landed on overwriting the
entrypointand prefixing my command with a-c, which is appended as an argument to the bash invocation. It's a bit confusing to me still, but it's functional: