-
Notifications
You must be signed in to change notification settings - Fork 1
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
[CORE-178] Fix integration tests #184
Conversation
Use the CRL_JANITOR_CLIENT_SA_B64 secret since it no longer exists in vault
5f0c6f7
to
10e5299
Compare
9a706f1
to
9a6b607
Compare
| jq .data > $AZURE_MANAGED_APP_FILE | ||
- name: Write Janitor Client SA file | ||
run: | | ||
JANITOR_SA_B64=${{ secrets.CRL_JANITOR_CLIENT_SA_B64 }} |
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.
This secret is no longer in vault so it gets handled separately
AZURE_MANAGED_APP_CLIENT_SECRET=$(jq -r '."client-secret"' ${AZURE_MANAGED_APP_CLIENT_FILE}) | ||
AZURE_MANAGED_APP_TENANT_ID=$(jq -r '."tenant-id"' ${AZURE_MANAGED_APP_CLIENT_FILE}) | ||
cat > ${AZURE_PROPERTIES_FILE} <<EOF | ||
AZURE_MANAGED_APP_CLIENT_ID=$(jq -r '."client-id"' ${AZURE_MANAGED_APP_FILE}) |
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.
This step was getting cached by github actions, but I needed it to re-run after updating the client secret so I just renamed some of the env variables.
@@ -24,7 +24,7 @@ public class AzureIntegrationUtils { | |||
"f557c728-871d-408c-a28b-eb6b2141a087", | |||
AzureEnvironment.AZURE); | |||
|
|||
public static final String DEFAULT_AZURE_RESOURCE_GROUP = "e2e-xmx74y"; | |||
public static final String DEFAULT_AZURE_RESOURCE_GROUP = "DefaultResourceGroup-EUS2"; |
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.
The "e2e-xmx74y" test resource group no longer exists and was causing AzureResponseLoggerTest.testRecordEvent
to fail
5a1672d
to
6abe557
Compare
6abe557
to
12a4082
Compare
|
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.
looks good, I see all tests passing, I did not do any testing myself
Ticket: https://broadworkbench.atlassian.net/browse/CORE-178