Skip to content

.#1482

Open
mccoystevens079-prog wants to merge 2368 commits intomicrosoft:app-deploy/2.3from
mccoystevens079-prog:master
Open

.#1482
mccoystevens079-prog wants to merge 2368 commits intomicrosoft:app-deploy/2.3from
mccoystevens079-prog:master

Conversation

@mccoystevens079-prog
Copy link
Copy Markdown

No description provided.

MikeRayMSFT and others added 30 commits September 23, 2024 14:27
Add hybrid compute-extension-last-connect
Bumps [rollup](https://github.com/rollup/rollup) from 2.79.1 to 2.79.2.
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v2.79.1...v2.79.2)

---
updated-dependencies:
- dependency-name: rollup
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Entity Relationship Diagram (ERD) of the major tables in Northwind sample database
for those developers [all?] favouring the visual approach !
I added a new image (alas should have a better description), but hope this PR may help someone.
…ples/features/security/always-encrypted-with-secure-enclaves/sample-application/AlwaysEncryptedConsole/Azure.Identity-1.11.4

Bump Azure.Identity from 1.11.0 to 1.11.4 in /samples/features/security/always-encrypted-with-secure-enclaves/sample-application/AlwaysEncryptedConsole
Bumps [serve-static](https://github.com/expressjs/serve-static) and [express](https://github.com/expressjs/express). These dependencies needed to be updated together.

Updates `serve-static` from 1.15.0 to 1.16.2
- [Release notes](https://github.com/expressjs/serve-static/releases)
- [Changelog](https://github.com/expressjs/serve-static/blob/v1.16.2/HISTORY.md)
- [Commits](expressjs/serve-static@v1.15.0...v1.16.2)

Updates `express` from 4.19.2 to 4.21.1
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/4.21.1/History.md)
- [Commits](expressjs/express@4.19.2...4.21.1)

---
updated-dependencies:
- dependency-name: serve-static
  dependency-type: indirect
- dependency-name: express
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [express](https://github.com/expressjs/express) from 4.19.2 to 4.21.1.
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/4.21.1/History.md)
- [Commits](expressjs/express@4.19.2...4.21.1)

---
updated-dependencies:
- dependency-name: express
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
…arn/samples/demos/azure-sql-edge-demos/Wind-Turbine-Demo/webappsrc/SqlDbEdgeDemoWeb/SqlDbEdgeDemo.Web/ClientApp/path-to-regexp-1.9.0

Bump path-to-regexp from 1.8.0 to 1.9.0 in /samples/demos/azure-sql-edge-demos/Wind Turbine Demo/webappsrc/SqlDbEdgeDemoWeb/SqlDbEdgeDemo.Web/ClientApp
…arn/samples/demos/azure-sql-edge-demos/Wind-Turbine-Demo/webappsrc/SqlDbEdgeDemoWeb/SqlDbEdgeDemo.Web/ClientApp/rollup-2.79.2

Bump rollup from 2.79.1 to 2.79.2 in /samples/demos/azure-sql-edge-demos/Wind Turbine Demo/webappsrc/SqlDbEdgeDemoWeb/SqlDbEdgeDemo.Web/ClientApp
…arn/samples/databases/wide-world-importers/wwi-app/wwwroot/lib/webcomponentsjs/multi-41ee8087b2

Bump serve-static and express in /samples/databases/wide-world-importers/wwi-app/wwwroot/lib/webcomponentsjs
…arn/samples/databases/wide-world-importers/wwi-app/wwwroot/lib/webcomponentsjs/express-4.21.1

Bump express from 4.19.2 to 4.21.1 in /samples/databases/wide-world-importers/wwi-app/wwwroot/lib/webcomponentsjs
Update Schema of existing dashboards and add new SQL Health Dashboard…
…whenthrow

Added rollback transaction before an exception is thrown
Bumps [cookie](https://github.com/jshttp/cookie) and [express](https://github.com/expressjs/express). These dependencies needed to be updated together.

Updates `cookie` from 0.6.0 to 0.7.1
- [Release notes](https://github.com/jshttp/cookie/releases)
- [Commits](jshttp/cookie@v0.6.0...v0.7.1)

Updates `express` from 4.20.0 to 4.21.1
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/4.21.1/History.md)
- [Commits](expressjs/express@4.20.0...4.21.1)

---
updated-dependencies:
- dependency-name: cookie
  dependency-type: indirect
- dependency-name: express
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
segovoni and others added 29 commits February 7, 2026 00:07
Delete samples/features/sql-big-data-cluster directory
Bumps [minimatch](https://github.com/isaacs/minimatch) from 3.1.2 to 3.1.5.
- [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md)
- [Commits](isaacs/minimatch@v3.1.2...v3.1.5)

---
updated-dependencies:
- dependency-name: minimatch
  dependency-version: 3.1.5
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Updating to allow restore with more parameters
Bumps [flatted](https://github.com/WebReflection/flatted) from 3.3.3 to 3.4.2.
- [Commits](WebReflection/flatted@v3.3.3...v3.4.2)

---
updated-dependencies:
- dependency-name: flatted
  dependency-version: 3.4.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Clarify description of AdventureWorks sample database.
Add arc-sql-license-type-compliance
Add new DeployIfNotExists policy, deployment and remediation scripts,
and documentation screenshots for enforcing LicenseType on Arc-enabled
SQL Server extensions.

New files:
- policy/azurepolicy.json: custom policy definition
- scripts/deployment.ps1: policy definition and assignment creation
- scripts/start-remediation.ps1: remediation task with role checks
- docs/screenshots/: visual references

Updated README paths for sql-server-samples repo structure.
Removed old flat policy files (params.json, policy.json, rules.json)
replaced by the new structured layout.
…arn/samples/databases/wide-world-importers/wwi-app/wwwroot/lib/webcomponentsjs/flatted-3.4.2

Bump flatted from 3.3.3 to 3.4.2 in /samples/databases/wide-world-importers/wwi-app/wwwroot/lib/webcomponentsjs
…arn/samples/databases/wide-world-importers/wwi-app/wwwroot/lib/webcomponentsjs/minimatch-3.1.5

Bump minimatch from 3.1.2 to 3.1.5 in /samples/databases/wide-world-importers/wwi-app/wwwroot/lib/webcomponentsjs
…res/optimized-locking

Optimized Locking - Transaction ID (TID) Locking internals sample
Add custom Azure Policy and scripts for Arc-enabled SQL Server license type configuration
Remove the full-repo git clone instruction and replace it with
targeted curl commands that download only the three required files
(policy/azurepolicy.json, scripts/deployment.ps1, scripts/start-remediation.ps1).

This avoids cloning the entire sql-server-samples repository, reducing
setup time and bandwidth for users who only need the Arc SQL license
type policy.

Changes:
- Add optional mkdir/cd step for a clean local working directory
- Add curl commands to fetch individual files into the expected
  policy/ and scripts/ folder structure
- Add note about curl alias on Windows PowerShell 5.1
- Remove git clone and deep cd instructions

No script changes required: deployment.ps1 resolves the policy JSON
via Join-Path relative to PSScriptRoot, which is preserved by the
new folder layout.
Change ManagementGroupId from required to optional in both
deployment.ps1 and start-remediation.ps1. When not specified,
the scripts resolve the tenant root management group ID
automatically via (Get-AzContext).Tenant.Id.

Changes:
- deployment.ps1: ManagementGroupId parameter now Mandatory=false;
  auto-resolves to tenant root group with informational output
- start-remediation.ps1: same parameter change and auto-resolve
- README.md: updated both parameter tables (Required=No, default
  shown as 'Tenant root group'); simplified examples to omit
  ManagementGroupId where the default suffices; added explicit
  management group examples for users who need a custom scope
Remove hardcoded license type references from policy displayName
and description. The actual target license type is controlled by
parameters at assignment time, so the definition metadata should
not imply a specific value.

Changes:
- azurepolicy.json: displayName and description now use generic
  'Configure Arc-enabled SQL Server license type' wording
- deployment.ps1: collapsed the PAYG/SA conditional display name
  logic into a single generic label per platform
Include the selected target license type in the policy definition
and assignment display names for clarity in the Azure Portal.

Format: Configure Arc-enabled SQL Server (<platform>) license type to '<label>'
Examples:
- Configure Arc-enabled SQL Server (All platforms) license type to 'Pay-as-you-go'
- Configure Arc-enabled SQL Server (Linux) license type to 'License With Software Assurance'

The azurepolicy.json description remains generic since the display
name is overridden by the script at definition creation time.
Restructure both Deploy Policy and Start Remediation usage
instructions to guide users through setting variables before
running scripts. Clearly separates required vs optional parameters
with inline comments, shows progressively detailed invocations
(minimal, with subscription, with all options), and streamlines
scenario examples with descriptive comments.
Sync changes from claestom/sql-arc-policy-license-config into the
sql-server-samples fork.

azurepolicy.json:
- Add ConsentToRecurringPAYG compliance checks in existenceCondition:
  when target is PAYG, resources must also have the consent property
  to be considered compliant (handles both new transitions and
  backward compatibility for pre-consent PAYG extensions)
- Add ConsentToRecurringPAYG to the deployment template: when target
  is PAYG, the remediation sets Consented=true with a UTC timestamp;
  non-PAYG targets use the base LicenseType-only settings
- Add consentTimestamp template parameter (auto-generated via utcNow)

deployment.ps1:
- Add retry loop (5 attempts, 10s delay) for managed identity role
  assignments to handle replication delays after policy assignment
  creation; also handles Conflict responses gracefully

README.md:
- Add Recurring Billing Consent (PAYG) section documenting the
  consent behavior, compliance evaluation, and immutability note
Improve usability of Arc SQL license type policy sample
@microsoft-github-policy-service
Copy link
Copy Markdown
Contributor

@mccoystevens079-prog please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

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.