Skip to content
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

Regenerated new workload ARM template and added missing module param #502

Merged
merged 2 commits into from
Nov 8, 2021

Conversation

brooke-hamilton
Copy link
Contributor

Description

Regenerated the ARM template from the Bicep template. Also fixed an issue in which the spokeType parameter was not being supplied for the workloadVirtualNetworkPeerings module.

Issue reference

The issue this PR will close: #501

Checklist

Please make sure you've completed the relevant tasks for this PR out of the following list:

  • All acceptance criteria in the backlog item are met
  • The documentation is updated to cover any new or changed features
  • Manual tests have passed
  • Relevant issues are linked to this PR

@brooke-hamilton
Copy link
Contributor Author

@glennmusa please verify that using workloadName is the right value to use for the spokeType parameter. A 'type' and a 'name' are not always the same thing, but in this case I think we should use the workload name as the spoke type so that we can support unique and multiple workload names. Or maybe I'm wrong and all new workloads should use the same value for spokeType.

@glennmusa
Copy link
Contributor

glennmusa commented Nov 5, 2021

@glennmusa please verify that using workloadName is the right value to use for the spokeType parameter. A 'type' and a 'name' are not always the same thing, but in this case I think we should use the workload name as the spoke type so that we can support unique and multiple workload names. Or maybe I'm wrong and all new workloads should use the same value for spokeType.

I think you're right that a type and a name are not the same thing. This looks like a miss on my part.

In fact, the spoke "Type" I created in the root module does use a name property and not a type property:

var spokes = [
{
name: 'operations'

I think the right thing to do here would be to rename the spokeType parameter to spokeName in the spokeNetworkPeering module to reflect that:

Good catch! Happy to pair up on the change if it bubbles up unwieldly.

Copy link
Contributor

@glennmusa glennmusa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree on your changes for spokeType => spokeName

@brooke-hamilton brooke-hamilton enabled auto-merge (squash) November 5, 2021 21:35
@brooke-hamilton
Copy link
Contributor Author

Agree on your changes for spokeType => spokeName

Done. Please re-review. 💯

@brooke-hamilton brooke-hamilton merged commit a2cf882 into main Nov 8, 2021
Copy link
Contributor

@glennmusa glennmusa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@brooke-hamilton brooke-hamilton deleted the brooke/newworkloadarm branch November 8, 2021 16:32
jwaltireland pushed a commit to ARPA-H/AzureMissionLZ that referenced this pull request Nov 14, 2024
…zure#502)

* Regenerated ARM template. Added spokeType param

* Renamed spokeType to spokeName
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tier 3 ARM template is out of sync with the Bicep template
2 participants