* updating package properties with direct/indirect (if named differently) as well as pulling BuildDocs from ci.yml artifact list if it exists
* eliminate the addition of buildDocs property. it requires powershell-yaml to be present on our base function. not good
* remove call to InitializeBuildDocs
---------
Co-authored-by: Scott Beddall <scbedd@microsoft.com>
* Add descriptive error when variable groups are not added to pipeline
* Add emoji to deploy step title to make it easier to find
* Move yaml json checking into powershell script
* Fix base sub config empty/string checking
---------
Co-authored-by: Ben Broderick Phillips <bebroder@microsoft.com>
* Regenerated to accomodate the latest API version (2024-07-01-preview), which adds in new batching and file APIs.
* Updated help text for the function parameters.
* Tests were literally doing nothing and weren't needed - we create clients all over the place using all the constructors.
* Remove empty section.
* Upload files works, and the other routes related to it _should_ work. Still need to test some more.
* Fixing a bug where I didn't need to pass in a pointer anymore.
* Very basic test for batches. The timing of the API makes it hard for us to test normally.
* Updated to handle an anonymous type
* Using latest commit from PR.
* updates for merged spec.
* fixed generation
* removing orphaned model
* updated recordings
* skipping test
* reducing coverage until we can reenable file tests.
* added comment about workaround
* removing orphaned type
* updated changelog
---------
Co-authored-by: Richard Park <ripark@microsoft.com>
* Refactor prepare-pipelines
* Convert pipeling generation single to use template
* Convert to pwsh for setting the variables
* Fix switch expression
* Add path separator in front of devopspath
* Continue on error for individual step failures
* Remove unnecessary parameters
---------
Co-authored-by: Wes Haggard <Wes.Haggard@microsoft.com>
Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>
Fixing a bug where we could end up getting our management link stuck.
The problem was basically a combination of errors:
1. We were missing the sender settlement mode, which made it so we were only 1/2 in the "receive and delete" mode that we intended to be.
2. Ignoring that, our AcceptMessage() call was actually load bearing and critical and _wasn't_ getting called in some cases, like if you cancelled the call.
* Incorporate common sub config changes to live testing
* Remove federated auth field from sdk yaml files
* Default federated auth mode to true in pipeline templates
* Remove secret based sub configs from yaml template
* Fix fed auth defaults for ci testing
* Fix missing service connection in overridden cloud configs
* Add missing file paths parameters
* Apply a few changes to Get-PRPackageProperties to make it more customizable for our users. Remove wonky gap + extra spacing that should pass the patch application process now that we've manually aligned common.ps1
* account for feedback -- rename CanaryPackages to AdditionalValidationPackages
* dependentPackagesforInclusion -> additionalValidationPackages
---------
Co-authored-by: Scott Beddall <scbedd@microsoft.com>
* bump proxy version
* bump proxy version
* restore most of the old performance, only fall back to json matching when something goes wrong
* use newest version with protection from invalid json
---------
Co-authored-by: Scott Beddall <scbedd@microsoft.com>
- Upgrading to latest go-amqp, which lets us errors.As() for the AMQP error.
- GetRecoveryKind() should check the AMQP errors's condition first as it has more specific information about what's broken
- Updated all the tests to account for this new possiblity (wrapped error being ignored in favor of the AMQP condition in the inner AMQP error)
- Deleted two unused error types (ErrConnectionClosed, ErrNotFound)
- Adding in some comments about areas that are a little tricky.
- Added in a test to make sure our connection based recovery works well using a real connection (we already do link based checks).
- Fixing an issue with the bicep - in stress your user doesn't have rights to apply RBAC roles.
Azure SDK Bot
Grace Wilcox
microsoft-github-policy-service[bot]
Charles Lowell
Ben Broderick Phillips
Scott Addie
Richard Park
Simon Moreno
Gerardo Lecaros
Wes Haggard
cn0238
Andrew Porter
tanyasethi-msft
Peng Jiahui