-
Notifications
You must be signed in to change notification settings - Fork 39
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
Deploy python-sdk on astro #1499
Conversation
Codecov ReportBase: 97.72% // Head: 93.16% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1499 +/- ##
==========================================
- Coverage 97.72% 93.16% -4.56%
==========================================
Files 21 91 +70
Lines 835 4845 +4010
Branches 0 479 +479
==========================================
+ Hits 816 4514 +3698
- Misses 19 239 +220
- Partials 0 92 +92
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@kaxil @tatiana @pankajastro is there any security concerns with having astro deployment as a part of CI/CD? Perhaps we should only do this with release branches instead of with the main branch? WDYT? |
Hi @dimberman We will run this only on the main branch as a nightly job and not on each merge. Also, CI/CD will take care of the deployment of our example DAG on astro cloud only and we have a master DAG which will take care of running our example DAG at the scheduled time. We do similar things in the provider. Please do let me know if you think there can be any specific potential security issues. |
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.
Maybe we should change the schedule for the benchmark job from '0 0 * * 1'
to '30 3 * * 1'
so that it is easier to separate out the jobs based on schedule events in the if conditionals and also we allow sufficient time for the deploy job to complete before running the benchmark script on Mondays.
5bafab5
to
69bb343
Compare
6c68160
to
511bd5d
Compare
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.
Let's please try to use https://github.com/astronomer/deploy-action
cc @tatiana
c2919fc
to
8ff6986
Compare
264e993
to
e03b907
Compare
Deploy astro CI job
a531e63
to
bee8eda
Compare
Created a separate ticket for this: #1742 |
# Description closes: #913 ## What is the current behavior? We want to run our example DAG on astro cloud and collect the result ## What is the new behavior? - Add a CI job which will trigger daily and deploy our example DAG and install astro-sdk from main branch in astro-cloud image - Add a master DAG which will trigger all example DAG ## Does this introduce a breaking change? No ### Checklist - [ ] Created tests which fail without the change (if possible) - [ ] Extended the README / documentation, if necessary --------- Co-authored-by: rajaths010494 <rajath.srinivasaiah@astronomer.io>
Description
closes: #913
What is the current behavior?
We want to run our example DAG on astro cloud and collect the result
What is the new behavior?
Does this introduce a breaking change?
No
Checklist