-
Notifications
You must be signed in to change notification settings - Fork 1
support private endpoints #449
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
072d935
to
7121c83
Compare
/run pipeline |
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.
1 comment - will be interesting to see how upgrade test reacts to this change. Hopefully its an update in place
/run pipeline |
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 expected the upgrade test to fail, but it passes. So I checked the code, and seem the wrong test function is being used for the upgrade test. Its using RunSchematicTest
and it should be using RunSchematicUpgradeTest
:
err := options.RunSchematicUpgradeTest()
if !options.UpgradeTestSkipped {
assert.Nil(t, err, "This should not have errored")
}
Please fix the upgrade test
Ran upgrade test locally and it fails:
|
52cd945
to
422a65b
Compare
/run pipeline |
8d1e8e8
to
5df337c
Compare
/run pipeline |
🎉 This PR is included in version 2.2.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
support private endpoints
for issue - #444 (comment)
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers