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

aio rt:action:create --config-file not working as expected as is not updating the actions called #681

Open
yrodrigez opened this issue Oct 24, 2024 · 0 comments

Comments

@yrodrigez
Copy link

Expected Behaviour

When creating an action listed in app.config.yaml, for example:
myAction.http

And when the Swagger file contains the following configuration:

"/myPath/": {
  "get": {
    "operationId": "myProject/myPackage/myAction.http",
    "responses": {
      "default": {
        "description": "Default response"
      }
    },
    "x-openwhisk": {
      "action": "myAction.http",
      "namespace": "myProject",
      "package": "myPackage",
      "url": "not-used"
    }
  }
}

When deploying the action using app.config.yaml, the API endpoint should be updated accordingly in the REST API configuration based on the latest deployment and Swagger configuration.

Actual Behaviour

  • The deployment does not consistently update the REST API configuration.
  • Sometimes the endpoint is deleted unexpectedly.
  • Other times, the endpoint uses outdated behavior from previous deployments rather than the most recent configuration

Reproduce Scenario (including but not limited to)

  1. Create an action in the app.config.yaml (e.g., myAction.http).
  2. Set up a Swagger file with a corresponding path (e.g., /myPath/) and x-openwhisk configuration pointing to the action.
  3. Deploy the action using aio app deploy (or another deployment method).
  4. Observe the following inconsistencies:
  • API endpoint not updating.
  • Endpoint being removed after deployment.
  • Endpoint using older action behavior despite the updated configuration

Steps to Reproduce

  1. Create an action in the app.config.yaml (e.g., myAction.http).
  2. Set up a Swagger file with a corresponding path (e.g., /myPath/) and x-openwhisk configuration pointing to the action.
  3. Deploy the action using aio app deploy (or another deployment method).
  4. Observe the following inconsistencies:
  • API endpoint not updating.
  • Endpoint being removed after deployment.
  • Endpoint using older action behavior despite the updated configuration

Platform and Version

10.3.1

Sample Code that illustrates the problem

Logs taken while reproducing problem

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