-
Notifications
You must be signed in to change notification settings - Fork 7
add monitor/schema action
#256
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
Conversation
Atlas Lint ReportAnalyzed migrations
Migrations automatically reviewed by Atlas |
||||||||||||||||
Atlas Lint ReportAnalyzed migrations2
Migrations automatically reviewed by Atlas |
||||||||||||||||
|
|
||||||||||||||||
Atlas detected changes to the desired schemaMigration Plan (View on Atlas Cloud)-- Create "t1" table
CREATE TABLE `t1` (
`c1` integer NOT NULL
);
-- Create "t2" table
CREATE TABLE `t2` (
`c1` integer NOT NULL
);
-- Create "t3" table
CREATE TABLE `t3` (
`c1` integer NOT NULL,
`c2` integer NOT NULL
);Atlas lint results
📝 Steps to edit this migration plan1. Run the following command to pull the generated plan to your local workstation: atlas schema plan pull --url "atlas://atlas-action/plans/pr-256-R1cGcSfo" > pr-256-R1cGcSfo.plan.hcl2. Open 3. Push the updated plan to the registry using the following command: atlas schema plan push --pending --env test --file pr-256-R1cGcSfo.plan.hcl4. Re-trigger the gh run rerun 11910339752 |
0f699b8 to
19725f6
Compare
98f4b37 to
ea49db6
Compare
032efa8 to
8ce6837
Compare
8ce6837 to
9062a75
Compare
526b9d7 to
c1a1590
Compare
c1a1590 to
f2db92a
Compare
f2db92a to
ab73a5c
Compare
masseelch
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| @@ -0,0 +1,36 @@ | |||
| name: 'Atlas Schema Monitor' | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| name: 'Atlas Schema Monitor' | |
| name: 'Atlas Schema Monitoring' |
example run: