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]Replace Tokens' version 3 (replacetokens@3) is deprecated #675

Open
karthikpeddi115 opened this issue Sep 30, 2024 · 1 comment
Open

Comments

@karthikpeddi115
Copy link

Release version

v6.0.1.1

Describe the bug

Even tried with replacetokens@5 and replacetokens@6, but not able to override the contents from qa config.yaml file.

apimServiceName: apiops-poc-sea-apim
namedValues:

  • name: test-backend-url
    properties:
    displayName: testbackendurl
    secret: false
    value: https://dev.ar.com/umbraco/api/content

  • name: test-cache-base-url
    properties:
    displayName: test-cache-base-url
    secret: false
    value: https://qa-ec-std.azurewebsites.net:443/api

  • name: test-cache-rewrite-url
    properties:
    displayName: test-cache-base-url
    secret: false
    value: /TestAPI/triggers/When_a_HTTP_request_is_received/invoke?api-version=2022-05-01&sp=%2Ftriggers%2FWhen_a_HTTP_request_is_received%2Frun&sv=1.0&sig=6dwYsmnQ_wSZkk3gKDazajr1

backends:
apis:
gateways:
groups:
products:
subscriptions:
tags:

Expected behavior

image
Need to override above namedvalues to above mentioned values.
Pipeline is success, but its not overrided.

Actual behavior

NamedValues should override.

Reproduction Steps

Update the configuration.qa.yaml file with namd values.
Run published pipline.

Copy link

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

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

No branches or pull requests

1 participant