ariga / atlas-action Goto Github PK

When using the Apply GitHub Action:

  migrate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: ariga/setup-atlas@v0
      - name: Deploy Atlas Migrations
        uses: ariga/atlas-action/migrate/apply@v1
        with:
          url: ${{ secrets.DATABASE_URL }}
          dir: db/schema.hcl

Where ${{ secrets.DATABASE_URL }} = postgres://db_user:[email protected]/name_db

Which seems to be a valid Postgres URL

I get the following error:

Run ariga/atlas-action/migrate/apply@v1
Using version v1
Downloading atlas-action binary: https://release.ariga.io/atlas-action/atlas-action-v1
Error: Error: unsupported driver ""
Error: The process exited with code 1

To see if my DATABASE_URL secret was the problem I tried to run manually the command atlas schema inspect
in the following way:

  test-atlas-connection:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v3
      
      - name: Set up Atlas CLI
        run: curl -sSf https://atlasgo.sh | sh


      - name: Inspect Database Schema
        run: atlas schema inspect --url ${{ secrets.DATABASE_URL }}
        env:
          ATLAS_NO_COLOR: "true"

And it worked successfully without error.

Thank you in advance, and let me know if more information is required.

Hello,

I was attempting to migrate to the new CI/CD workflows and noticed a bug in ariga/atlas-action/migrate/lint@v1.

The error was provided: Error: slug must be lowercase alphanumeric and may contain /.-_

From what I can gather, my dir-name unfortunately has uppercase characters, and is causing the linting action to fail.

When the action runs I can see it correctly detects backwards incompatible changes.

However, I wasn't able to work out how to cause a non-zero exit code, which could then be used to make the workflow go into a failed state.

If I were running the CLI I would configure an atlas.hcl with:

lint {
    incompatible {
        error = true
    }
}

But there doesn't seem to be a way to pass in an --config parameter as an input to this action.

I'd like to use my re-usable scripts for generating diffs in github actions w/ atlas CLI. I'd like to use the atlas-action to set up atlas for me. However, this does not seem to be supported right now, as:

1. the binary is not exposed for later steps
2. it's not possible to run the atlas-action without executing any command

Do you think it's possible to support that, or with a separate action like ariga/setup-atlas?

link: https://github.com/tensorchord/envd-server/actions/runs/3648121383/jobs/6161170673

Message:

Error: Resource not accessible by integration

Kinda a follow-up to #112, I wanted to test the action and pin it to a commit. But it seems like the option is to run your actions with ...@vVERSION or ...@master. Neither might be desirable to test unreleased code.

The offending lines are here:
https://github.com/ariga/atlas-action/blob/master/shim/index.js#L18-L28

Is there a good reason to bail there?

Hello!

I'd like to drop a table on purpose but I get the error DS102 which is expected.
How can I instruct Atlas on letting this go because it's on purpose?

Thank you for your time!

I understand that you all are a commercial enterprise but it would be nice to allow users to indicate that they would not to see the ariga cloud warning if a token is not provided. Some organizations may have a longer path to commercial/contractual engagement and the warning could actually serve as an adoption barrier in the context of a POC or evaluation.

The url should be "https://auth.atlasgo.cloud/signup" instead of "http://auth.ariga.cloud/signup"

Seems like it's fixed in master, but not relased?

action.yml says required false:
https://github.com/ariga/atlas-action/blob/master/migrate/lint/action.yml#L12-L14

Is it possible to fix atlas CLI version to be used during action run?
It seems that currently latest atlas is used.