Investigate custom actions for publishing Bicep types

[sk593]

Area for Improvement

There are multiple workflows where we need to publish Bicep types to ACR. Some steps when we do this overlap between workflows. We should investigate if these can be moved to a custom action and reused across workflows.

Observed behavior

An example workflow for publish Bicep can be found here:

radius/.github/workflows/build.yaml

Line 266 in 875c5ca

name: Publish Radius bicep types to ACR

Desired behavior

We should have a custom action for the publish Bicep steps and reuse that action in our workflows.

Proposed Fix

We should add a custom actions workflow for publishing Bicep types. This would handle the setup steps like generating types, uploading artifacts, and publishing to ACR. This way, if we need to update the publish steps, we only need to update as single actions workflow as opposed to multiple areas.

rad Version

GH version of radius

Operating system

No response

Additional context

No response

Would you like to support us?

• Yes, I would like to support you

AB#13049

[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

[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

[radius-triage-bot]

👋 @sk593 we need more information.

To help us investigate further, we need additional information to reproduce or understand this issue. Please ensure you have steps to reproduce and information about your OS, rad CLI version, and runtime version.

A project maintainer will reply on this issue soon to ask for additional specifics if needed.

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

[ytimocin]

Can you add more information on what we are improving here @sk593? Like what are the measurable downsides of the current design vs what we want to have with this issue? For example, we would need to update in a few different places instead of one and that would require more time.