Given we cannot create subfolders under .github\workflow folder
and we have repos that want additional workflows then we have
in the tools repo we need to setup a file pattern matching for
the sync processing to only sync the ones we want to be common.
For now just use the existing *event* pattern but we can move them
to another pattern similar to *common* or *sync* in the future as
we add more common workflows.
* we want the path that we write to to be defined by literalpath, otherwise files with [ or ] will break powershell when writing the file to disk
* slight wording adjustment so the command can be invoked directly
* Add RestAPISpecsDocsRepos to branch cleanup.
* Remove commented out yml, add pre-message to limit output and output core limit at the start of processing
* updates for feedback
* more compatibility with expanding/contracting packages. add ability for packages to have DependentPackages that must be included in the set of packages that should be built given a changeset
---------
Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>
* Update apiview prod to staging sync job to use managed identity
* Update job name
* Add python install step and update as per review comment
* Connect to cosmos DB using key
* apiview_sync_pipeline
* Changes to return exit code
* Add new line
* Add chain credential to support cli credential
* Fix broken Tests
* Refactor Models into Separate Files. Get Tests to all pass
* All Tests Green
* Enable Test Job on the pipeline
* Move Projects to DotNET 8
* Enable CLient Side Tests
* Switch back to net 7
* update SPA tests
* Resolve Bug in First Release Approval Button
* Remove rougue file
* add additional argument to Save-Package-Properties to allow for usage in pull request context
---------
Co-authored-by: Scott Beddall (from Dev Box) <scbedd@microsoft.com>
Co-authored-by: Scott Beddall <45376673+scbedd@users.noreply.github.com>
Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>
* Set storage account test resources to disable blob public access
* Skip adding network rules to storage accounts that don't need them during cleanup
* Add succeeded check to set pipeline subnet info step
* Disable network firewall by default in resource creation/removal
* Document federated identity credential auth in stress clusters
* Add custom storage cluster to stress infra configs. Update AKS base version
* Update tools/stress-cluster/chaos/README.md
Co-authored-by: Richard Park <51494936+richardpark-msft@users.noreply.github.com>
* Update tools/stress-cluster/chaos/README.md
Co-authored-by: Richard Park <51494936+richardpark-msft@users.noreply.github.com>
* Update tools/stress-cluster/chaos/README.md
Co-authored-by: Richard Park <51494936+richardpark-msft@users.noreply.github.com>
* Update tools/stress-cluster/chaos/README.md
Co-authored-by: Richard Park <51494936+richardpark-msft@users.noreply.github.com>
* Support regex/negative regex filters for stress test discovery. Add storage env defaults
* Add storage environment pipeline and deploy conditionals for stress
* Update addons changelog
* Doc feedback
---------
Co-authored-by: Richard Park <51494936+richardpark-msft@users.noreply.github.com>
* Support storage network access and worm removal in remove test resources script
* Move storage network access script to common resource helpers file
* Improve storage container deletion resilience
* Plumb through pool variable to live test cleanup template
* Add sleep for network rule application
* Restrict live test storage account access to client IP
* Add storage pools to test resources vnet allowlist
* Use pool subnet map to reduce number of subnets added to live test resources
* snap
* Add test resource parameter to add ip ranges to storage firewall
* Validate and update ip firewall rules
* Get pool subnet using separate workload identity
* correct all the necessary release phases. update the determine release tags script. (going to go to semver usage before this pr merges)
* params -> param
* re-enable release phase
* remove launchsettings
Without this building and pushing from ARM Mac's (or any ARM platform) produce images that just fail with mysterious errors because AKS and your local arch don't match.
* created a 'publish nmp artifact using esrp' which ALSO forces a set of build stages onto 1es templates
* migrated our existing prod facing npm package artifacts to utilize this new template
* All npm tooling now is security compliant + released through ESRP
* Merge subscription configuration file values with the supplied subscription config
* Bring forward working parts
* Collapse into a single task
* SubConfig-Helpers.ps1 changes
* Update remove-test-resources.yml