Skip to content

test commit #35

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

test commit #35

wants to merge 1 commit into from

Conversation

ronenlu
Copy link
Member

@ronenlu ronenlu commented Mar 24, 2025

No description provided.

@datdao
Copy link
Member

datdao commented Mar 24, 2025

atlas migrate lint on migrations

Status Step Result
No migration files detected  
ERD and visual diff generated View Visualization
No issues found View Report
Read the full linting report on Atlas Cloud

@datdao
Copy link
Member

datdao commented Mar 24, 2025

atlas migrate lint on sqlite-wrong-sum

Status Step Result
1 new migration file detected atlas.sum
ERD and visual diff generated View Visualization
Migration Integrity Check
File atlas.sum is invalid
checksum mismatch
Read the full linting report on Atlas Cloud

@datdao
Copy link
Member

datdao commented Mar 24, 2025

Atlas detected changes to the desired schema

Migration Plan (View on Atlas Cloud)

-- Create "t1" table
CREATE TABLE "public"."t1" (
  "c1" integer NOT NULL,
  "c2" integer NOT NULL
);
-- Set comment to table: "t1"
COMMENT ON TABLE "public"."t1" IS 'a2e4abed618e20c72a41b9f57927ccd1fe6f063b';

Atlas lint results

Status Step Result
Detect schema changes2 new statements detected
No issues found

📝 Steps to edit this migration plan

1. Run the following command to pull the generated plan to your local workstation:

atlas schema plan pull --url "atlas://circleci-schema-test/plans/a2e4abed618e20c72a41b9f57927ccd1fe6f063b" > a2e4abed618e20c72a41b9f57927ccd1fe6f063b.plan.hcl

2. Open a2e4abed618e20c72a41b9f57927ccd1fe6f063b in your editor and modify it as needed. Note that the result of the plan should align
the database with the desired state. Otherwise, Atlas will report a schema drift.

3. Push the updated plan to the registry using the following command:

atlas schema plan push --pending --file a2e4abed618e20c72a41b9f57927ccd1fe6f063b.plan.hcl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants