Investigating infra pipeline logic #285
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
with the benefits devcontainer
test_init_db_command fails with user count 26 != asserted 25
move version to within app __init__
more realistic and end-to-end test of the infrastructure and app
|
The infra pipeline ran 
The code (i.e. condition for running |
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm opening this to see what the Azure pipeline does when opening a PR from
devintotest.Based on the code, it seems like it will run
terraform applyon the "test" workspace even though all we did was open a PR. This implies theterraform applythat runs on merging the PR would be a no-op. (I'm not actually going to merge this PR. Just want to look at the results of opening the PR.)