-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: failed to run: Error: data.remote_dir.this: reading remote dir: input: dir Sorry, something went wrong #9
Comments
2023-10-11T05:28:27.3332971Z Requested labels: ubuntu-latest 2023-10-11T05:29:16.0310091Z Post job cleanup. |
Hey @jay-babu, Thanks for the detailed report. I looked into your case and as far as I can tell it's caused by an incompatibility on our side between the sync and deploy actions. Each migration directory on Atlas Cloud has two identifiers, one is "name" (transformity-db in your case) and the second is "slug" ("app" in your case). In the past directories only had a "name", which the sync action selects based on the repo/path. The issue stems from the way the current We are actually just about to announce a new generation of GitHub Actions which streamlines all of these issues so its really unfortunate that you hit this thing today :-) To fix this you can use the new action instead of
The first step installs atlas and logs in to Atlas cloud. The second step deploys. HTH |
I am getting this error now. I deleted my project from atlas because I thought that was the reason why but doesn't seems to be the case
|
|
Hello,
I have tried quite a bit to set up deployments with atlas to my database and am getting the error in the title.
Workflow:
https://github.com/Transformity/pos-db/blob/main/.github/workflows/ci-atlas.yaml
Logs:
https://github.com/Transformity/pos-db/actions/runs/6478371279/job/17590035202
The text was updated successfully, but these errors were encountered: