[#1567] Resolving NGINX authentication misconfiguration in resync workflow for Cardano Node and DBSync #1569
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
In order to facilitate the execution of the resync action in various environments (development, testing, and staging), the NGINX authentication configuration has been updated. Previously, authentication was controlled using a single `NGINX_BASIC_AUTH` secret. This has now been expanded to include separate authentication secrets for development (`DEV_NGINX_BASIC_AUTH`), testing (`TEST_NGINX_BASIC_AUTH`), and staging (`STAGING_NGINX_BASIC_AUTH`), allowing more granular control and enhanced security in different stages of deployment.
Ryun1
approved these changes
Jul 12, 2024
placek
deleted the
fix/1567-resolving-nginx-authentication-misconfiguration-in-resync-workflow-for-cardano-node-and-dbsync
branch
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.
The purpose of these changes is to address the issue where NGINX authentication settings were either missing or incorrectly named in the resync workflow for Cardano Node and DBSync. By updating the NGINX authentication configuration, the intention is to ensure that the resync action can be performed properly across different environments.