Correction of hostname when no user domainname #1
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
§{PublicAlbHostname} already contains protocol (see outputs from 03-publicalb.yaml)
vrioux
pushed a commit
that referenced
this pull request
Jan 31, 2023
Creating updated revision to support moodle 4.1 with graviton2 support
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.
§{PublicAlbHostname} already contains protocol (see outputs from 03-publicalb.yaml)
As defined today, the result of $proto . strtolower($hostname) is ‘http://http://monalb.region.elb.amazonaws.com’ resulting in a faulty configuration file and impossibility to connect. In fact, in 03-publicalb.yaml template, depending on existing sslcertificates or not, already indicates the protocol (http:// or https://).