Skip to content

Missing wskadmin tool configuration docs #16

@ricardozanini

Description

@ricardozanini

Hi!
I was trying to create a custom namespace to configure the packages and to expose my web actions through the API Gateway.
The API Gateway seems to work only with custom namespaces. My bet is that the whisk.admin namespace isn't supposed to be accessed externally. What I'm missing in this tutorial is how to set up the wskadmin tool.

Running the wskadmin tool, it claims that some env variables are missing:

property "DB_WHISK_AUTHS" not found in environment or property file
property "WHISK_LOGS_DIR" not found in environment or property file
property "DB_PASSWORD" not found in environment or property file
property "DB_PORT" not found in environment or property file
property "DB_PROTOCOL" not found in environment or property file
property "DB_WHISK_ACTIONS" not found in environment or property file
property "DB_HOST" not found in environment or property file
property "DB_WHISK_ACTIVATIONS" not found in environment or property file
property "DB_USERNAME" not found in environment or property file

I think it needs to connect directly to the CouchDB. That put, we should expose the routes on OpenShift directly? Could someone give some advice of how to make this work? I could write a chapter here helping others how to properly configure it. :)

Many thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions