Test nginx docker ports#1926
Closed
alxndrsn wants to merge 21 commits into
Closed
Conversation
Previously called `disallow-all`; rename to `backend-strict` to better reflect its usage rather than current implementation details.
Looks like a merge error.
Switch from Content-Security-Policy-Report-Only to Content-Security-Policy.
Switch from Content-Security-Policy-Report-Only to Content-Security-Policy.
It looks like the checkout code from the `test-images` job was copy/pasted elsewhere. Simplifying this config should speed up git checkout in affected jobs.
Fixes: expected docker context is increased due to WF merge
Fixes/install openssl
The `DB_SSL` env var was made illegal in getodk#1647. The check was then moved from runtime to build time in getodk#1671. Checking at build-time allows for faster failure and clearer feedback to sysadmins who are upgrading, and previously depended on this env var. However, the downside is that if container images are pre-built centrally, this check will be skipped. With this commit, the check will move to container startup. However, it will now be skipped if the container is started with a non-standard CMD/command/COMMAND.
Switch all headers from `Content-Security-Policy-Report-Only` to `Content-Security-Policy`.
Restrict TCP ports to the local machine. This will prevent exposing these dev services on the local network or wider.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Closes #
What has been done to verify that this works as intended?
Why is this the best possible solution? Were any other approaches considered?
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Does this change require updates to documentation? If so, please file an issue here and include the link below.
Before submitting this PR, please make sure you have:
nextbranch OR only changed documentation/infrastructure (masteris stable and used in production)