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

fix: Update avm/ptn/lz/sub-vending -- Bug fixes and improvements #4274

Open
wants to merge 39 commits into
base: main
Choose a base branch
from

Conversation

sebassem
Copy link
Contributor

@sebassem sebassem commented Jan 23, 2025

Description

  • Update modules versions
  • Switch to private endpoints for the deployment script instead of service endpoints
  • Added PublicnetworkAccess:Disabled to the storage account due to a recent change in policy
  • Update CI pipeline to pin Az.Accounts and Az,Subscription modules' versions due to a recent bug
  • Update deployment script naming to avoid duplicate names

Pipeline Reference

Pipeline
avm.ptn.lz.sub-vending

Type of Change

  • Update to CI Environment or utilities (Non-module affecting changes)
  • Azure Verified Module updates:
    • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
      • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
      • The bug was found by the module author, and no one has opened an issue to report it yet.
    • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
    • Breaking changes and I have bumped the MAJOR version in version.json.
    • Update to documentation

Checklist

  • I'm sure there are no other open Pull Requests for the same update/change
  • I have run Set-AVMModule locally to generate the supporting module files.
  • My corresponding pipelines / checks run clean and green without any errors or warnings

…script and update download commands to use Invoke-WebRequest
@sebassem sebassem requested review from a team as code owners January 23, 2025 13:21
@avm-team-linter avm-team-linter bot added the Needs: Core Team 🧞 This item needs the AVM Core Team to review it label Jan 23, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Triage 🔍 Maintainers need to triage still label Jan 23, 2025

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue label Jan 23, 2025

Important

If this is a module-related PR, being submitted by the sole owner of the module, the AVM core team must review and approve it (as module owners can't approve their own PRs).

To indicate this PR needs the core team''s attention, apply the "Needs: Core Team 🧞" label!

The core team will only review and approve PRs that have this label applied!

@sebassem sebassem changed the title Fix: Sub-vending bug fixes and improvements fix: Sub-vending bug fixes and improvements Jan 23, 2025
@@ -74,4 +74,6 @@ runs:
# Set agent up
Set-EnvironmentOnAgent -PSModules $modules
#Import-module Az.Subscription -MinimumVersion 0.11.1
Copy link
Contributor

Choose a reason for hiding this comment

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

Leftover

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Resolved

@eriqua eriqua changed the title fix: Sub-vending bug fixes and improvements fix: Update avm/ptn/lz/sub-vending -- Bug fixes and improvements Jan 26, 2025
@eriqua eriqua added Class: Pattern Module 📦 This is a pattern module Type: CI 🚀 This issue is related to the AVM CI and removed Needs: Triage 🔍 Maintainers need to triage still labels Jan 26, 2025
@@ -269,6 +269,7 @@ function Invoke-ResourceRemoval {
if ($subscriptionState -eq 'Enabled') {
Write-Verbose ('[*] Disabling resource [{0}] of type [{1}]' -f $subscriptionName, $Type) -Verbose
if ($PSCmdlet.ShouldProcess("Subscription [$subscriptionName]", 'Remove')) {
Import-Module Az.Accounts -MinimumVersion 4.0.1
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this still required here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, it only worked when I specified this here, I can remove it once the agents use the latest version of this module by default

@@ -45,7 +45,7 @@ runs:
# Define PS modules to install on the runner
$modules = @(
@{ Name = 'Az.Accounts' },
@{ Name = 'Az.Accounts'; Version = '4.0.2' },
Copy link
Contributor

Choose a reason for hiding this comment

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

Please add a comment here to explain why this version so if we ever want to allow any never version than 4.0.2 and retest we know which module this was for. The same applies to the other explicit version your hardcoded below.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Class: Pattern Module 📦 This is a pattern module Needs: Core Team 🧞 This item needs the AVM Core Team to review it Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: CI 🚀 This issue is related to the AVM CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants