[DTOSS-11410] - fix(infra): Fix smoke test for production apex domain configuration #592
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.
Fix smoke test for production apex domain configuration
Description
Fixed smoke test script to support apex domain configuration for production environment. The smoke test was failing because it was constructing URLs as
{env}.{domain}/shafor all environments, but production uses an apex domain configuration (use_apex_domain = true) which requires just{domain}/sha.Changes Made
1. Updated smoke test script
USE_APEX_DOMAINparameter (5th parameter) tocontainer_app_smoke_test.shUSE_APEX_DOMAIN=true: useshttps://{DNS_ZONE_NAME}/shaUSE_APEX_DOMAIN=false: useshttps://{ENV_CONFIG}.{DNS_ZONE_NAME}/shahttps://pr-{PR_NUMBER}.{DNS_ZONE_NAME}/shafalsefor backward compatibility2. Updated GitHub workflow
.github/workflows/stage-4-deploy.yamlto extractuse_apex_domainfrom environment'svariables.tfvarsuse_apex_domainvalue as 5th parameter to smoke test script"false"if variable not present in tfvars3. Added documentation
docs/infrastructure/infra-faq.mdTesting
Tested locally with: