Revert bicep build authentication workaround

[sk593]

Area for Improvement

There are a few places in our code where we had to implement workarounds because of this issue: Azure/bicep#14774. The workaround is explained in the issue and removes az auth

Observed behavior

No response

Desired behavior

Once there is a fix for the above issue, we should remove the workarounds in our validate-bicep and functional test workflows

Places we use the workaround:

radius/.github/workflows/functional-test-cloud.yaml

Line 376 in 3ddb61e

"cloud": {

radius/.github/workflows/functional-test-noncloud.yaml

Line 349 in 3ddb61e

"cloud": {

radius/.github/workflows/validate-bicep.yaml

Line 72 in 3ddb61e

jq '. + {"cloud": {"credentialPrecedence": ["Environment"]}}' bicepconfig.json > tmp.json && mv tmp.json bicepconfig.json

Proposed Fix

No response

rad Version

GH actions radius version

Operating system

No response

Additional context

No response

Would you like to support us?

• Yes, I would like to support you

AB#12961

[radius-triage-bot]

👋 @sk593 Thanks for filing this issue.

A project maintainer will review this issue and get back to you soon.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

[brooke-hamilton]

Area for Improvement

There are a few places in our code where we had to implement workarounds because of this issue: Azure/bicep#14774. The workaround is explained in the issue and removes az auth

@sk593 can you please add a link to the workaround.

[radius-triage-bot]

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

[sk593]

Area for Improvement

There are a few places in our code where we had to implement workarounds because of this issue: Azure/bicep#14774. The workaround is explained in the issue and removes az auth

@sk593 can you please add a link to the workaround.

Sure, the workaround is mentioned in the linked issue. This is the comment that explains the workaround: Azure/bicep#14774 (comment)

[kachawla]

Area for Improvement

There are a few places in our code where we had to implement workarounds because of this issue: Azure/bicep#14774. The workaround is explained in the issue and removes az auth

@sk593 can you please add a link to the workaround.

Sure, the workaround is mentioned in the linked issue. This is the comment that explains the workaround: Azure/bicep#14774 (comment)

@sk593 this came up in triage discussion, it was meant for link to code paths where we have implemented the workaround. Could you please update the issue description to include those links? Mainly to make it easily discoverable for whoever picks this issue up.

[sk593]

Area for Improvement

There are a few places in our code where we had to implement workarounds because of this issue: Azure/bicep#14774. The workaround is explained in the issue and removes az auth

@sk593 can you please add a link to the workaround.

Sure, the workaround is mentioned in the linked issue. This is the comment that explains the workaround: Azure/bicep#14774 (comment)

@sk593 this came up in triage discussion, it was meant for link to code paths where we have implemented the workaround. Could you please update the issue description to include those links? Mainly to make it easily discoverable for whoever picks this issue up.

ah, I misunderstood the comment. just added the code links