Skip to content

Conversation

@stack72
Copy link
Contributor

@stack72 stack72 commented Oct 14, 2025

{
  "schemaName": "AWS::EC2::Subnet",
  "schemaId": "01JK0QZHF6ZSY6JFM39MBCRJ4C",
  "category": "AWS::EC2",
  "installed": true,
  "upgradeAvailable": true
}

You can specify a POST to /upgrade with a dryRun param:

curl -X 'POST' \
  'http://localhost:5380/v1/w/01HPJ3K7RC486W9RPR3T0B6HS2/change-sets/01K779TQWFCYZA60YT41DWV7BZ/schemas/01JK0QZHF6ZSY6JFM39MBCRJ4C/upgrade' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "dryRun": true
}'

the result is:

{
  "success": false,
  "breakingChanges": [
    {
      "path": "/domain/EnableLniAtDeviceIndex",
      "changeType": "typeChanged",
      "oldType": "integer",
      "newType": "number"
    },
    {
      "path": "/domain/Ipv4NetmaskLength",
      "changeType": "typeChanged",
      "oldType": "integer",
      "newType": "number"
    },
    {
      "path": "/domain/Ipv6NetmaskLength",
      "changeType": "typeChanged",
      "oldType": "integer",
      "newType": "number"
    }
  ],
  "dryRun": true
}

@github-actions
Copy link

github-actions bot commented Oct 14, 2025

Dependency Review

✅ No vulnerabilities or OpenSSF Scorecard issues found.

Scanned Files

None

For an installed schema, we should see if there's an upgrade available
and if so, add the ability to upgrade the schema
@stack72 stack72 force-pushed the luminork-upgrade-schema branch from 10e7e78 to ba474f1 Compare October 14, 2025 01:06
@stack72 stack72 requested a review from britmyerss October 14, 2025 01:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants