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

error:API resource location is not registered on Azure devops Server (URL) #285

Open
indreshmourya1106 opened this issue Apr 4, 2023 · 3 comments

Comments

@indreshmourya1106
Copy link

HI Team ,
i am getting error "error:API resource location is not registered on Azure devops Server (URL)" while trying to map rule.
We are using docker image of aggregator and have on prim azure devops server.
kindly help

@indreshmourya1106
Copy link
Author

can anyone help here? I am not able to test it via command after docker configuration , we have on prim azure devops server ,version 2022 RC1

@giuliov
Copy link
Member

giuliov commented Apr 20, 2023

Configuring docker is complex. Given that I do not have a lab with 2022 RC1, the only way to help you is have details on what you have done (which version are you using, which checklist you followed, verbose logging, etc.) and what is failing (a mispelled name can cause errors).
Do not underestimate that you have the source code, can debug and pinpoint the exact line of code that is not working.

@indreshmourya1106
Copy link
Author

Configuring docker is complex. Given that I do not have a lab with 2022 RC1, the only way to help you is have details on what you have done (which version are you using, which checklist you followed, verbose logging, etc.) and what is failing (a mispelled name can cause errors). Do not underestimate that you have the source code, can debug and pinpoint the exact line of code that is not working.

We have docker host machine which has windows server 2019 and On prim azure devops Server 2022 RC1.We are trying to configure TFS aggregator for enable some rule for Azure devops server.

We have done below step so far :

• DNS entry for Aggregator
• generated a valid certificate in .pfx format (matches the above)
• pulled the docker image (docker pull tfsaggregator/aggregator3:latest)
• prepare apikeys.json
• copied the pfx and json files above in a secrets directory on the docker host
• writtene the rule files
• copied the rule files in a rules directory on the docker host
• ran the container, mounting both the secrets and rules directories, and defining the Aggregator_SharedSecret environment variable.

docker run --rm -it -p 5320:5320 -e Aggregator_SharedSecret=********** -e Aggregator_VstsToken=********** -e ASPNETCORE_Kestrel__Certificates__Default__Password="" -e Aggregator_SharedSecret= --mount type=bind,source=c:/src/github.com/tfsaggregator/aggregator-cli/docker/secrets/,target=c:/secrets --mount type=bind,source=c:/src/github.com/tfsaggregator/aggregator-cli/docker/rules/,target=c:/rules tfsaggregator/aggregator3:latest

Now I am not sure what should I do next

@jessehouwing jessehouwing transferred this issue from tfsaggregator/tfsaggregator Jul 13, 2023
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

2 participants