-
Notifications
You must be signed in to change notification settings - Fork 11
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 integration tests #88
base: main
Are you sure you want to change the base?
Conversation
260afcf
to
3c01a6d
Compare
3c01a6d
to
95eab62
Compare
91581c9
to
2b8318b
Compare
2b8318b
to
97909b9
Compare
97909b9
to
df37ee3
Compare
These integration tests are mostly good to go now, the documentation from Talos makes it much easier to manually deploy docker instances in maintenance mode so that we can test the full life cycle. One of the options required for this however, is only available in more recent versions of Talos. So we'll need to get the provider updated to support newer versions first. I'm not sure if a Talos upgrade is completely blocked by the issues we currently have with compsite inputs -> outputs. I don't know if that feature is a super high priority for the Pulumi team at this time, so it would be nice if we could find a way to upgrade Talos before that feature gets implemented. I gave the For me at least, I think there's still more investigation to be done. |
c22ddd0
to
d88e957
Compare
Does the PR have any schema changes?Looking good! No breaking changes found. Maintainer note: consult the runbook for dealing with any breaking changes. |
8e55e0b
to
7100c63
Compare
# Conflicts: # examples/examples_test.go Add health check and update checked-in examples version Increase read timeout Clean up and add testcontainer # Conflicts: # go.work.sum # Conflicts: # examples/go.mod # Conflicts: # examples/examples_nodejs_test.go # examples/examples_test.go # examples/go.mod # examples/go.sum gomodtidy # Conflicts: # examples/go.mod # examples/go.sum Update compose from docs In some cases the project name "talos" conflicts with the provider name Add configuration for integration tests Update @types/node to 20 upgrade go deps # Conflicts: # examples/go.mod # examples/go.sum gomodtidy after rebase # Conflicts: # examples/go.sum Remove check for project id gomodtidy again
7100c63
to
f13cb76
Compare
This provider can be kinda tough to test, add some integration tests for validation.
The YAML SDK seems to have issues at the moment, with integration tests hopefully it will be easier to sus out what is wrong.