-
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
feat!: remove Azure SQL DB restore workflow #349
Conversation
@equinor/ops-coredev Do you think that this should be a breaking change instead, so that v9 marks the beginning of this repo being a collection of workflows that rely on some sort of source code? Ref. #339. So PR would be updated like this:
|
Yeah i think that makes sense, that way we can sort of have it like a clean slate, as in it would be easier to read future updates, just like you how you wrote it with v9 being the begining. |
I agree with @kov117. It makes a lot of sense. |
It makes sense for it to be a breaking change, given the scope of this repo is "breaking" with the previous scope. Go for it 🎉 I kinda like the idea of having a collection of the automated operations, where |
@helenakallekleiv Yes, this workflow would typically be implemented as an Azure Automation runbook in either equinor/ops-automation or a new equinor/ops-runbooks. |
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.
👍🏽
Fixes #339