humanitec / preview-envs-action Goto Github PK

When I do this:

- name: create preview environment
  uses: humanitec/preview-envs-action@v1
  with:
    humanitec-token: ${{ secrets.HUMANITEC_TOKEN }}
    humanitec-org: humanitec-labs
    humanitec-app: dev-docs
    action: create
    github-token: ${{ secrets.GITHUB_TOKEN }}

I got this error:

Created environment: dev-ephemeral-envs, https://app.humanitec.io/orgs/***/apps/onlineboutique/envs/dev-ephemeral-envs
Created auto-deployment rule for refs/heads/ephemeral-envs and image registry.humanitec.io/***/hello-humanitec
Error: Action failed
Error: HttpError Resource not accessible by integration

I think it would be ideal to provide the option to just create a new Env for an App without providing any image. Think about subsequent tasks to deploy Score, etc.

Does that make sense?

Today the id and the name of the ephemeral Env is auto-generatead, it would be ideal to have the option to provide the id if in my organization we need to respect a certain naming convention for our Envs in Humanitec.

For create, providing the id will set the name with it? Assuming that's reasonable, otherwise adding another input name...

https://github.com/humanitec/preview-envs-action/blob/main/src/utils.ts

It would be great if we could have a dedicated action that we could use to comment the PR with insightful information like:

• View in Humanitec - link to the
• EnvId
• List and links of all the DNS of the App deployed
• Deployment Diff/Output
• ...

This is a typically workflow with PR for testing feature branch, especially with new/ephemeral envs.

Something around these lines (credit to @williamoverton for that!), see attached.

Kind of different from create and notify, why not comment, comment-summary or `get-summary?

This action could/should wait for the in-progress Deployment.

Kind of what is done in there: https://github.com/Humanitec-DemoOrg/ephemeral-env-demo/blob/main/.github/workflows/pull_request.yaml.