Skip to content

Conversation

@souvikghosh04
Copy link
Contributor

Why make this change?

  • Reference associated issue using # syntax. e.g. Closes #XX
    • Include summary (1-2 sentences) of linked issue to avoid redirecting reviewers to different pages.
    • Include links to any additional discussion threads related to this change.

What is this change?

  • Summary of how your changes work to give reviewers context of your intent.
    • Links to relevant documentation / StackOverflow, if applicable.

How was this tested?

  • Integration Tests
  • Unit Tests

Sample Request(s)

  • Example REST and/or GraphQL request to demonstrate modifications
  • Example of CLI usage to demonstrate modifications
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04 souvikghosh04 force-pushed the Usr/sogh/mcpconfigentities.v3 branch from bd45309 to a7a5921 Compare November 18, 2025 05:44
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
- Used config-generator.ps1 to regenerate config from scratch
- Properties now in correct order: rest  graphql  mcp  permissions
- Removed deprecated 'dml-tools' setting from mcp section
- This matches the output from the latest DAB CLI and should fix snapshot test failures
- Regenerated dab-config files for: MsSql, MySql, PostgreSql, CosmosDB, DwSql
- All configs now have consistent property order: rest  graphql  mcp  permissions
- Removed deprecated settings where applicable
- Ensures pipeline snapshot tests use configs generated by latest DAB CLI
@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
Problem:
The DAB CLI ignores --graphql.operation parameter when adding/updating
stored procedures, defaulting them to 'mutation' instead of 'query'.
This breaks tests expecting 'executeGetPublisher' query field names.

Solution:
1. Added --graphql.operation query to GetBooks add/update commands
2. Added --graphql.operation query to GetPublisher update command
3. Added post-processing in config-generator.ps1 to manually fix operations
   for GetBooks and GetPublisher after generation

This ensures the pipeline generates configs with correct GraphQL operations,
fixing the 5 failing MsSql stored procedure tests in CI/CD.

Updated MsSql config and snapshot to match pipeline output.
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
- Add --graphql.operation query to GetBooks add command
- Fix GetBooks and GetPublisher update commands to use lowercase query
- Extend post-processing script to also handle DwSql configs
- Regenerate dab-config.DwSql.json with correct query operations
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04 souvikghosh04 force-pushed the Usr/sogh/mcpconfigentities.v3 branch from b928be7 to bf781c6 Compare November 20, 2025 12:31
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04 souvikghosh04 force-pushed the Usr/sogh/mcpconfigentities.v3 branch from 656ad20 to bd129d9 Compare November 20, 2025 16:14
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
…ed to output directory

This fixes Linux test failures where the post-processed DwSql config with correct stored procedure operations (query vs mutation) was not being copied to the test output directory.
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
@souvikghosh04
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 6 pipeline(s).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants