You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hannes-ucsc opened this issue
Dec 4, 2019
· 1 comment
Assignees
Labels
compliance[subject] Information and software securitydebt[type] A defect incurring continued engineering costdemoed[process] Successfully demonstrated to teamorange[process] Done by the Azul teamssp[process] Resolution is reflected in SSPtest[subject] Unit and integration test code
There are now various places in the unit tests where us-east-1 is hard-coded as the AWS region. This is the region that our real deployments live in. Apparently, some moto mocks require a region to be set (the one for SQS, for example). To accommodate those but also as a second line of defence against mocks becoming ineffective and real resources being used, the test setup at a very high level, potentially AzulTestCase.setupClass() should patch AWS_DEFAULT_REGION to some other region, potentially even a made up one.
┆Issue is synchronized with this Jira Story
┆Project Name: azul
┆Issue Number: AZUL-921
The text was updated successfully, but these errors were encountered:
hannes-ucsc
added
debt
[type] A defect incurring continued engineering cost
test
[subject] Unit and integration test code
compliance
[subject] Information and software security
labels
Dec 4, 2019
compliance[subject] Information and software securitydebt[type] A defect incurring continued engineering costdemoed[process] Successfully demonstrated to teamorange[process] Done by the Azul teamssp[process] Resolution is reflected in SSPtest[subject] Unit and integration test code
There are now various places in the unit tests where
us-east-1
is hard-coded as the AWS region. This is the region that our real deployments live in. Apparently, some moto mocks require a region to be set (the one for SQS, for example). To accommodate those but also as a second line of defence against mocks becoming ineffective and real resources being used, the test setup at a very high level, potentiallyAzulTestCase.setupClass()
should patch AWS_DEFAULT_REGION to some other region, potentially even a made up one.┆Issue is synchronized with this Jira Story
┆Project Name: azul
┆Issue Number: AZUL-921
The text was updated successfully, but these errors were encountered: