chore: add disable_postgres flag and separate from stack_api disabling #1558
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
tippenein
changed the title
Codecov ReportAttention: Patch coverage is 📢 Thoughts on this report? Let us know! |
tippenein
force-pushed
the
chore/separate-postgres-from-stacks-api
branch
2 times, most recently
from
2077c20
to
5f59d3f
Compare
tippenein
force-pushed
the
chore/separate-postgres-from-stacks-api
branch
from
5f59d3f
to
e7d2247
Compare
tippenein
force-pushed
the
chore/separate-postgres-from-stacks-api
branch
from
fcc3e76
to
3764feb
Compare
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.
In order to use clarinet's devnet for testing the api functionality we needed a way of disabling one or the other
disable_postgresfield in Devnet.toml is essentially the main addition here, but also implies thatdisable_stacks_apino longer disables postgres which it did do previously