-
Notifications
You must be signed in to change notification settings - Fork 173
Consolidate custom_domain and tre_url settings into single tre_url setting #4631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: marrobi <[email protected]>
Co-authored-by: marrobi <[email protected]>
custom_domain and tre_url settings are confusing
marrobi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update the changelog highlighting the breaking change as per previous breaking changes.
Also increment the core infra version.
docs/tre-admins/setup-instructions/cicd-pre-deployment-steps.md
Outdated
Show resolved
Hide resolved
…nd increment core version Co-authored-by: marrobi <[email protected]>
Updated changelog with breaking change entry and incremented core version from 0.16.3 to 0.17.0. Commit: 054a60a |
marrobi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
/test |
|
🤖 pr-bot 🤖
(in response to this comment from @marrobi) |
|
@copilot please fix the build issue with Build Validation / Lint (pull_request) |
Co-authored-by: marrobi <[email protected]>
Fixed yamllint violations in config.sample.yaml by wrapping long lines to comply with 80-character limit. The build lint check should now pass. Commit: d51066a |
|
@copilot still get: 2025-07-17 11:57:53 [ERROR] Found errors in [shellcheck] linter!
|
Co-authored-by: marrobi <[email protected]>
|
@copilot one issue left: |
Co-authored-by: marrobi <[email protected]>
|
/test 647e657 |
|
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/16346481303 (with refid (in response to this comment from @marrobi) |
This PR consolidates the confusing
custom_domainandtre_urlsettings into a singletre_urlsetting as requested in issue #4248. Previously, users had to understand the difference between these two similar settings that served essentially the same purpose.Changes Made
Configuration Simplification
custom_domainfromconfig.sample.yamlandconfig_schema.jsontre_urlto accept full custom URLs (e.g.,https://mytre.example.com)tre_urlcan be either auto-generated or customBackend Implementation
extract_domain_from_url.shhelper function to programmatically extract domains from URLsload_and_validate_env.shto automatically deriveCUSTOM_DOMAINfromTRE_URLfor backward compatibility--custom-domainparameter and auto-detect custom domains from TRE URLDocumentation Updates
CUSTOM_DOMAINas deprecatedtre_urlapproachMigration Path
Before:
After:
Backward Compatibility
CUSTOM_DOMAINenvironment variable continue to work (automatically derived fromTRE_URL)letsencrypt.shscript works without modificationTesting
This change eliminates user confusion while maintaining full functionality and backward compatibility.
Fixes #4248.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.