Dredd: apiaryApiKey & apiaryApiName are no longer working from dredd.yml config

Created on 24 May 2019  路  6Comments  路  Source: apiaryio/dredd

Describe the bug
apiaryApiKey & apiaryApiName are no longer working from dredd.yml config since 10.0.0

To Reproduce
1) dredd init
- added apiary key
- added apiary name
2) write simple apiary.apib
3) dredd
4) now i can see the following message:

warn: 
Apiary API Key or API Project Subdomain were not provided.
Configure Dredd to be able to save test reports alongside your Apiary API project:
https://dredd.org/en/latest/how-to-guides/#using-apiary-reporter-and-apiary-tests

Expected behavior
It should use apiaryApiKey & apiaryApiName variables

What is in your dredd.yml?

color: true
dry-run: null
hookfiles: null
language: nodejs
require: null
server: python manage.py runserver
server-wait: 3
init: false
custom:
  apiaryApiKey: my-api-key
  apiaryApiName: my-api-name
names: false
only: []
reporter: apiary
output: []
header: []
sorted: false
user: null
inline-errors: false
details: false
method: []
loglevel: warning
path: []
hooks-worker-timeout: 5000
hooks-worker-connect-timeout: 1500
hooks-worker-connect-retry: 500
hooks-worker-after-connect-wait: 100
hooks-worker-term-timeout: 5000
hooks-worker-term-retry: 500
hooks-worker-handler-host: 127.0.0.1
hooks-worker-handler-port: 61321
config: ./dredd.yml
blueprint: apiary.apib
endpoint: 'http://127.0.0.1:3000'

What's your dredd --version output?

dredd v11.1.4 (Darwin 18.6.0; x64)

Does dredd --loglevel=debug uncover something?

If you run Dredd with debugging output, do you see any interesting information relevant to the bug?

  • No
bug

Most helpful comment

I think lib/CLI.js:334 should look like cliConfig.custom = R.mergeDeepRight(this.custom, cliConfig.custom);

All 6 comments

I think lib/CLI.js:334 should look like cliConfig.custom = R.mergeDeepRight(this.custom, cliConfig.custom);

That's possible, we did refactor this part very recently. Would you send a fix in a PR? 馃檹

@skazancev Do you need any guidance? I'm happy to help if you got stuck on something.

i'm sorry, i've missed first comment. Yes, i can send a fix in a PR :)

Hi, @skazancev. Could you please confirm this issue is solved for you? Thanks.

Hi, @skazancev. Could you please confirm this issue is solved for you? Thanks.

Hello! Yes, it is. Thank you :)

Was this page helpful?
0 / 5 - 0 ratings