-
Notifications
You must be signed in to change notification settings - Fork 102
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
Add CI tests for different target connection configs #75
Conversation
encrypt: yes | ||
trust_cert: yes | ||
azuresql_sqlcred: &azuresql | ||
<<: *sqlserver |
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.
For my understanding, is this a way to extend de above mentioned profiles, the ones with &<some name>
?
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.
that's right!
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.
they're called YAML anchors, and I'm on the fence about them legibility-wise. Seems pretty easy to go overboard on. how would you rate the readability of this YAML file, @JCZuurmond?
https://support.atlassian.com/bitbucket-cloud/docs/yaml-anchors/
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.
I like the anchors, indeed you should not use it too much, but it narrows what your focusing on within each segment. For example with sqlserver_local_encrypt
it is clear that encrypt: yes
and trust_cert: yes
is what should be tested - it's like a fixture in testing
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.
I like it!
encrypt: yes | ||
trust_cert: yes | ||
azuresql_sqlcred: &azuresql | ||
<<: *sqlserver |
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.
that's right!
Great Work! |
for #65. basically now we have 3 different target configs to test against:
Encrypt
andTrustServerCertificate
aren't specifiedEncrypt
andTrustServerCertificate
are specifiedConnection types still lacking coverage are:
windows_login=True
because it would require a Windows VM, but we can open a new PR for that in the future.az cli
shortly anyway@Mikael any must have connection type coverage? If not, I'd say let's merge this so we can: