Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] datafactory@2018-06-01: webactivities.typeproperties.headers does not match the real response #27816

Open
ziyeqf opened this issue Feb 18, 2024 · 0 comments
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Data Factory Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@ziyeqf
Copy link
Contributor

ziyeqf commented Feb 18, 2024

API Spec link

API Spec version

2018-06-01

Describe the bug

the definition of headers was changed on 97cefc8#diff-d5aa9217e2132932fec24cba8c2a103430c34ed925739a4529a0acd16483803aR8246

While the API still return in the original format:

                    "headers": {
                        "authorization": {
                            "type": "Expression",
                            "value": "@pipeline().parameters.test"
                        },
                        "content_type": "application/x-www-form-urlencoded"
                    }

which does not match the Swagger

Expected behavior

the Swagger definition and the response keep consistent

Actual behavior

they are not consistent

Reproduction Steps

add an expression via Portal and call GET on the resource, the difference shows.

Environment

No response

@ziyeqf ziyeqf added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Feb 18, 2024
@raych1 raych1 added Service Attention Workflow: This issue is responsible by Azure service team. Data Factory labels Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Data Factory Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants